Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05267631d383e0a09f2cb54b49455faa5b6b4c394c681e3f2301d79f50d33dcb

Tx prefix hash: 6ecafd6dc488127bd93739c597cdcbbf5faad539c40a20095133104c722112ea
Tx public key: 5ade7571b2e626d9994e0fb01d12e7c1fd57ad28c79e3cff211eb79be2dceaca
Timestamp: 1713920573 Timestamp [UCT]: 2024-04-24 01:02:53 Age [y:d:h:m:s]: 01:193:23:03:00
Block: 1007150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397255 RingCT/type: yes/0
Extra: 015ade7571b2e626d9994e0fb01d12e7c1fd57ad28c79e3cff211eb79be2dceaca02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b25ccffdd744c059a488e7c4ca3997f46d0e7bd78f6b3f6c3435eeca437b9ffa 0.600000000000 1468400 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": 1007160, "vin": [ { "gen": { "height": 1007150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b25ccffdd744c059a488e7c4ca3997f46d0e7bd78f6b3f6c3435eeca437b9ffa" } } ], "extra": [ 1, 90, 222, 117, 113, 178, 230, 38, 217, 153, 78, 15, 176, 29, 18, 231, 193, 253, 87, 173, 40, 199, 158, 60, 255, 33, 30, 183, 155, 226, 220, 234, 202, 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