Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e718ab72e2bfcdae4eec224f44106f8fad288b766d37c1c64bf3a0c7785e3941

Tx prefix hash: 6e1631674b13cc5d629f8240a4283e7cf021fdf0d1fae0ece99303d9b1c97a3d
Tx public key: 7047c128fbc9588b1e399c40ac34ad83801ecc072de2d004623f667313f851f8
Timestamp: 1741503168 Timestamp [UCT]: 2025-03-09 06:52:48 Age [y:d:h:m:s]: 00:257:17:09:04
Block: 1235371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181923 RingCT/type: yes/0
Extra: 017047c128fbc9588b1e399c40ac34ad83801ecc072de2d004623f667313f851f8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0d56251e1b6182aad1d8dc372833f8a79caf1201184c4899cb2819b90176da 0.600000000000 1722310 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": 1235381, "vin": [ { "gen": { "height": 1235371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0d56251e1b6182aad1d8dc372833f8a79caf1201184c4899cb2819b90176da" } } ], "extra": [ 1, 112, 71, 193, 40, 251, 201, 88, 139, 30, 57, 156, 64, 172, 52, 173, 131, 128, 30, 204, 7, 45, 226, 208, 4, 98, 63, 102, 115, 19, 248, 81, 248, 2, 17, 0, 0, 0, 1, 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