Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32116313de9f7a22e53e196ad7faf2f9a63503578be1bdd5b726d8e6bc8a3d46

Tx prefix hash: 0321457b9da55c3bfd6e14667b8face81c0b429e13df3ba27ade5fefecf8aebb
Tx public key: fdaae937b6c5b8ddd5369903666af8c92acf602dd3514b6408897f433dd5d408
Timestamp: 1650376498 Timestamp [UCT]: 2022-04-19 13:54:58 Age [y:d:h:m:s]: 03:005:10:01:04
Block: 483611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 784435 RingCT/type: yes/0
Extra: 01fdaae937b6c5b8ddd5369903666af8c92acf602dd3514b6408897f433dd5d408021100000002faf35c9c000000000000000000

1 output(s) for total of 15.331908899000 dcy

stealth address amount amount idx
00: 8f0dd3f10848a762191701d77ae95f35001ae0b96c2a64502211431bdcdf244f 15.331908899000 905322 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": 483621, "vin": [ { "gen": { "height": 483611 } } ], "vout": [ { "amount": 15331908899, "target": { "key": "8f0dd3f10848a762191701d77ae95f35001ae0b96c2a64502211431bdcdf244f" } } ], "extra": [ 1, 253, 170, 233, 55, 182, 197, 184, 221, 213, 54, 153, 3, 102, 106, 248, 201, 42, 207, 96, 45, 211, 81, 75, 100, 8, 137, 127, 67, 61, 213, 212, 8, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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