Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d47dc601add15dfba9c1a8985f844a4e5e772e13091ae007274fd3af57e5d34c

Tx prefix hash: 8ab3b0e3c6b44f47552871b8370b1002da00685af636bb232f70e58b72c6221c
Tx public key: 2b21d1fc0df7e0b4cb90458a1afb0d54b4412906c9f94217386fa6b19886a087
Timestamp: 1733416414 Timestamp [UCT]: 2024-12-05 16:33:34 Age [y:d:h:m:s]: 00:109:03:55:34
Block: 1168683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77804 RingCT/type: yes/0
Extra: 012b21d1fc0df7e0b4cb90458a1afb0d54b4412906c9f94217386fa6b19886a087021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c01335d491b1cc41619a3fa4e50035b6ac9c2b0d57bc515ffb3d9fab31d103d0 0.600000000000 1654394 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": 1168693, "vin": [ { "gen": { "height": 1168683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c01335d491b1cc41619a3fa4e50035b6ac9c2b0d57bc515ffb3d9fab31d103d0" } } ], "extra": [ 1, 43, 33, 209, 252, 13, 247, 224, 180, 203, 144, 69, 138, 26, 251, 13, 84, 180, 65, 41, 6, 201, 249, 66, 23, 56, 111, 166, 177, 152, 134, 160, 135, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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