Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d85f5183a65bbd45e47f730742f423be99e7165425fd323702bd852e2e68a9

Tx prefix hash: 1dda1a8c6cc48c4c36cb37e8cdc4fdcb7e50fd8465d01c5bd899527d6d9337d4
Tx public key: db70e5cbc30b1c6ccd9678d85f4d16bedf431c25fce45d77372a703721c60a02
Timestamp: 1751277360 Timestamp [UCT]: 2025-06-30 09:56:00 Age [y:d:h:m:s]: 00:137:08:29:43
Block: 1315768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96355 RingCT/type: yes/0
Extra: 01db70e5cbc30b1c6ccd9678d85f4d16bedf431c25fce45d77372a703721c60a020211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cb02407319071d5b7d244be56c9eff36501fedf1ae2c9beceb46ab21ac35db1 0.600000000000 1803423 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": 1315778, "vin": [ { "gen": { "height": 1315768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb02407319071d5b7d244be56c9eff36501fedf1ae2c9beceb46ab21ac35db1" } } ], "extra": [ 1, 219, 112, 229, 203, 195, 11, 28, 108, 205, 150, 120, 216, 95, 77, 22, 190, 223, 67, 28, 37, 252, 228, 93, 119, 55, 42, 112, 55, 33, 198, 10, 2, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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