Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e972dc73e0f5be0d9d22285fb801f749678bf539cde5118549e574b16a1eec2

Tx prefix hash: f37060f043f391b9f0146f471bf5eb8eee215e8dad34c4d7b4683ee704a20a1d
Tx public key: 64703e32185887ab7ad67a52e59bdf781b1f4fa03d0afe3e342f245bfb171437
Timestamp: 1709704021 Timestamp [UCT]: 2024-03-06 05:47:01 Age [y:d:h:m:s]: 01:047:15:48:18
Block: 972206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295053 RingCT/type: yes/0
Extra: 0164703e32185887ab7ad67a52e59bdf781b1f4fa03d0afe3e342f245bfb1714370211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae4a6ea5eacc0950051eba4f43686f00453e5e63b1c3d299a4377e9ef1efaea5 0.600000000000 1432113 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": 972216, "vin": [ { "gen": { "height": 972206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae4a6ea5eacc0950051eba4f43686f00453e5e63b1c3d299a4377e9ef1efaea5" } } ], "extra": [ 1, 100, 112, 62, 50, 24, 88, 135, 171, 122, 214, 122, 82, 229, 155, 223, 120, 27, 31, 79, 160, 61, 10, 254, 62, 52, 47, 36, 91, 251, 23, 20, 55, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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