Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6476b328cfb8cf296f967b3bb7faf9da13dfb5ebb274a996b5421271c7941fd

Tx prefix hash: e6d0391bb9f5c33f16712031a96495e4ff4fb591cc67fa7276d5f6d4b3a1c324
Tx public key: 598fbbc3c2d6427c18b435c85d2696e35e5f8d3d8ab7abdb61d43ba204deba1b
Timestamp: 1742714814 Timestamp [UCT]: 2025-03-23 07:26:54 Age [y:d:h:m:s]: 00:050:12:09:04
Block: 1245399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36119 RingCT/type: yes/0
Extra: 01598fbbc3c2d6427c18b435c85d2696e35e5f8d3d8ab7abdb61d43ba204deba1b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0724e0acb19890a3e24e7d4ba8dd18d6fe8e0343d3c3a2adc9fb2df74be5e98 0.600000000000 1732390 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": 1245409, "vin": [ { "gen": { "height": 1245399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0724e0acb19890a3e24e7d4ba8dd18d6fe8e0343d3c3a2adc9fb2df74be5e98" } } ], "extra": [ 1, 89, 143, 187, 195, 194, 214, 66, 124, 24, 180, 53, 200, 93, 38, 150, 227, 94, 95, 141, 61, 138, 183, 171, 219, 97, 212, 59, 162, 4, 222, 186, 27, 2, 17, 0, 0, 0, 2, 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