Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2456cae6a17ecb3fc10db99cf610bfd35233f6bfb0f824fef21a28535ad0c14

Tx prefix hash: 6dad00e74fedabb92f24192416f2a9f354e9d7ff344374da31a2e093b6edc02e
Tx public key: 2c16648d5b26511ef56f1f7adaebaa28aaeb481b4f66045e7c489c1c5796bb46
Timestamp: 1710310871 Timestamp [UCT]: 2024-03-13 06:21:11 Age [y:d:h:m:s]: 01:060:20:51:47
Block: 977238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304505 RingCT/type: yes/0
Extra: 012c16648d5b26511ef56f1f7adaebaa28aaeb481b4f66045e7c489c1c5796bb4602110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b032ace096fb6faf2bea7d322f53dcdfad12d9bee88d900ecb326a8ee9af6bdf 0.600000000000 1437239 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": 977248, "vin": [ { "gen": { "height": 977238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b032ace096fb6faf2bea7d322f53dcdfad12d9bee88d900ecb326a8ee9af6bdf" } } ], "extra": [ 1, 44, 22, 100, 141, 91, 38, 81, 30, 245, 111, 31, 122, 218, 235, 170, 40, 170, 235, 72, 27, 79, 102, 4, 94, 124, 72, 156, 28, 87, 150, 187, 70, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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