Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4b7353fcfb08eddbb38d267293541a6fc0ce5f80b14942affb4c346e3489bee2

Tx prefix hash: abe47986f05d1333bd48862a67c5674814b2eea37669e6c36540b5319d0c9072
Tx public key: 3e049d818e73fdcbebf7f79ff75fcda3f44933d3d8351e07c3d517f2a7b3825d
Timestamp: 1693414041 Timestamp [UCT]: 2023-08-30 16:47:21 Age [y:d:h:m:s]: 01:220:18:13:35
Block: 837333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418882 RingCT/type: yes/0
Extra: 013e049d818e73fdcbebf7f79ff75fcda3f44933d3d8351e07c3d517f2a7b3825d021100000007e6d27f9c000000000000000000

1 output(s) for total of 1.031735212000 dcy

stealth address amount amount idx
00: bb6d3f47011f2c5ec56e4448b6e46ad54a904a3e1a5bc5aa53af1cb3a4a69191 1.031735212000 1289951 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 837343, "vin": [ { "gen": { "height": 837333 } } ], "vout": [ { "amount": 1031735212, "target": { "key": "bb6d3f47011f2c5ec56e4448b6e46ad54a904a3e1a5bc5aa53af1cb3a4a69191" } } ], "extra": [ 1, 62, 4, 157, 129, 142, 115, 253, 203, 235, 247, 247, 159, 247, 95, 205, 163, 244, 73, 51, 211, 216, 53, 30, 7, 195, 213, 23, 242, 167, 179, 130, 93, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8