Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b53ebc77371d8b74cf55c3e3e75a619d2482e26319ffde851963c42d66d9ab6

Tx prefix hash: 6fb45a575e79c24f8055b8534fdf0f5370f0ae6e9cf4b7befa331778f8044f4d
Tx public key: 460429a720b229770bddcf0f2e9acc463ce3ec0d34f9519ade3ceb73dd4075e4
Timestamp: 1715602907 Timestamp [UCT]: 2024-05-13 12:21:47 Age [y:d:h:m:s]: 00:340:17:27:22
Block: 1021128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243519 RingCT/type: yes/0
Extra: 01460429a720b229770bddcf0f2e9acc463ce3ec0d34f9519ade3ceb73dd4075e402110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29aa8ca7931cd1aad3e765c16cb0bd4baa72c52cae6a288c43188ab7c36163a2 0.600000000000 1485345 of 15

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": 1021138, "vin": [ { "gen": { "height": 1021128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29aa8ca7931cd1aad3e765c16cb0bd4baa72c52cae6a288c43188ab7c36163a2" } } ], "extra": [ 1, 70, 4, 41, 167, 32, 178, 41, 119, 11, 221, 207, 15, 46, 154, 204, 70, 60, 227, 236, 13, 52, 249, 81, 154, 222, 60, 235, 115, 221, 64, 117, 228, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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