Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6f1737da1fc05d6f0f4f0cd0967f776b2b25250dd7c198c93881082c0c7979

Tx prefix hash: 6c175dabc7fc8ab0df8c6756a3a77aebcc467e71972d8478aa2dadc400768cf1
Tx public key: 9048bf54498888f2ffe63c6852aad2a44a1b44c4be9f243fccde2d4c66fef48d
Timestamp: 1702095806 Timestamp [UCT]: 2023-12-09 04:23:26 Age [y:d:h:m:s]: 01:038:00:25:58
Block: 909112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288539 RingCT/type: yes/0
Extra: 019048bf54498888f2ffe63c6852aad2a44a1b44c4be9f243fccde2d4c66fef48d02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df2d59746bce91e15ce4a7e35b22153a5f4ffbc2bbd4f2f95bd14bbf44401c6d 0.600000000000 1366177 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": 909122, "vin": [ { "gen": { "height": 909112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df2d59746bce91e15ce4a7e35b22153a5f4ffbc2bbd4f2f95bd14bbf44401c6d" } } ], "extra": [ 1, 144, 72, 191, 84, 73, 136, 136, 242, 255, 230, 60, 104, 82, 170, 210, 164, 74, 27, 68, 196, 190, 159, 36, 63, 204, 222, 45, 76, 102, 254, 244, 141, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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