Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a7a5b0f8738fed1bb1851c467e1180dc805ecb2f83bf7e995215283040068f1

Tx prefix hash: bc56514bbb2ddfe19bb50b510fefd4c78aac98ccdd3f584d865e8072ecbf590c
Tx public key: 4ea05812b46653d818ec6acb179a8c3bfc152ee775b5fe0fe9be9c54b52dedd1
Timestamp: 1701435347 Timestamp [UCT]: 2023-12-01 12:55:47 Age [y:d:h:m:s]: 01:197:16:52:25
Block: 903640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402403 RingCT/type: yes/0
Extra: 014ea05812b46653d818ec6acb179a8c3bfc152ee775b5fe0fe9be9c54b52dedd102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.622107646000 dcy

stealth address amount amount idx
00: b9afec828070bc3481d41491dd307a085d0160ffa34016297d0e1a0a20ed02b2 0.622107646000 1360325 of 0

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": 903650, "vin": [ { "gen": { "height": 903640 } } ], "vout": [ { "amount": 622107646, "target": { "key": "b9afec828070bc3481d41491dd307a085d0160ffa34016297d0e1a0a20ed02b2" } } ], "extra": [ 1, 78, 160, 88, 18, 180, 102, 83, 216, 24, 236, 106, 203, 23, 154, 140, 59, 252, 21, 46, 231, 117, 181, 254, 15, 233, 190, 156, 84, 181, 45, 237, 209, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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