Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6515149da7abca623a6ab01ebcf3d7889bd54a6a81f030bad425984f184efb22

Tx prefix hash: afccf8c5ab7a6171760a27bfde562bbdea8f67c294a44e48e482f2dbb4af788e
Tx public key: df6ac6a106ec13061c5b093cfcada62f2614c9a834bee59925e8379334c5890f
Timestamp: 1577555954 Timestamp [UCT]: 2019-12-28 17:59:14 Age [y:d:h:m:s]: 05:306:12:56:42
Block: 33677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366657 RingCT/type: yes/0
Extra: 01df6ac6a106ec13061c5b093cfcada62f2614c9a834bee59925e8379334c5890f02110000008dc3a1a09f000000000000000000

1 output(s) for total of 474.703538266000 dcy

stealth address amount amount idx
00: 56a8476643adf451f128ca6b9a5b169adb3dad297fd0b88d834e2f8f638da11e 474.703538266000 56476 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": 33687, "vin": [ { "gen": { "height": 33677 } } ], "vout": [ { "amount": 474703538266, "target": { "key": "56a8476643adf451f128ca6b9a5b169adb3dad297fd0b88d834e2f8f638da11e" } } ], "extra": [ 1, 223, 106, 198, 161, 6, 236, 19, 6, 28, 91, 9, 60, 252, 173, 166, 47, 38, 20, 201, 168, 52, 190, 229, 153, 37, 232, 55, 147, 52, 197, 137, 15, 2, 17, 0, 0, 0, 141, 195, 161, 160, 159, 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