Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e10d86e4a467394038311d9ee48e143fe8be5e93a5fc7d36181d8f8745c812ef

Tx prefix hash: d1cbfb14cda61c6399244ca161c6759f262ae28f9e32a2ed355715db9f68fc4f
Tx public key: 8e8207e5f9ba1ffd2e81ebf7877dc358e164462bb879bc2d114eafb979a5649b
Timestamp: 1731322307 Timestamp [UCT]: 2024-11-11 10:51:47 Age [y:d:h:m:s]: 01:009:22:43:31
Block: 1151328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265528 RingCT/type: yes/0
Extra: 018e8207e5f9ba1ffd2e81ebf7877dc358e164462bb879bc2d114eafb979a5649b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d95f8fd3cd10b8a243461fb05be85fe8e282ca9b436215ed2a4c7b1e382063 0.600000000000 1636841 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": 1151338, "vin": [ { "gen": { "height": 1151328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d95f8fd3cd10b8a243461fb05be85fe8e282ca9b436215ed2a4c7b1e382063" } } ], "extra": [ 1, 142, 130, 7, 229, 249, 186, 31, 253, 46, 129, 235, 247, 135, 125, 195, 88, 225, 100, 70, 43, 184, 121, 188, 45, 17, 78, 175, 185, 121, 165, 100, 155, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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