Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df1d64200dd324f68fc8bcd888785afa180dd69f0d2c66bbec95aaf598ae37e5

Tx prefix hash: 99099114ec39dded0073b1cd3d063147803d2bf8234c45878b9ac90d10f1583e
Tx public key: aa4dce703125d3d3deb2c388f7cf47ae3cc26b1402b75aa13e46cc43b9b7b31c
Timestamp: 1574729474 Timestamp [UCT]: 2019-11-26 00:51:14 Age [y:d:h:m:s]: 04:346:14:39:19
Block: 17551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129629 RingCT/type: yes/0
Extra: 01aa4dce703125d3d3deb2c388f7cf47ae3cc26b1402b75aa13e46cc43b9b7b31c021100000001f95225a5000000000000000000

1 output(s) for total of 536.842798534000 dcy

stealth address amount amount idx
00: f453842a11466c95f6f2c119088f4eed170cbbd7ab15df17d69dceb646ceb059 536.842798534000 25682 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": 17561, "vin": [ { "gen": { "height": 17551 } } ], "vout": [ { "amount": 536842798534, "target": { "key": "f453842a11466c95f6f2c119088f4eed170cbbd7ab15df17d69dceb646ceb059" } } ], "extra": [ 1, 170, 77, 206, 112, 49, 37, 211, 211, 222, 178, 195, 136, 247, 207, 71, 174, 60, 194, 107, 20, 2, 183, 90, 161, 62, 70, 204, 67, 185, 183, 179, 28, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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