Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47a83ed04a218fcec60b565a292c34f109ab635506d7e0faebc3142a75786b89

Tx prefix hash: aea4e09a78bbc897df3d6212708d8761369127087dd78eec4d1359825af98bd6
Tx public key: 6b4ff736de8933cd39df514fef481f95b20b2504f4081e4e254fdeb89d63cd8a
Timestamp: 1577208232 Timestamp [UCT]: 2019-12-24 17:23:52 Age [y:d:h:m:s]: 05:071:15:26:23
Block: 30922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200924 RingCT/type: yes/0
Extra: 016b4ff736de8933cd39df514fef481f95b20b2504f4081e4e254fdeb89d63cd8a0211000000acac34bf9e000000000000000000

1 output(s) for total of 484.778598276000 dcy

stealth address amount amount idx
00: 44ba20c8a8d8aa0dc51288fb31aeff041c13c644edf9d5653dd027e6e30bf64f 484.778598276000 51044 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": 30932, "vin": [ { "gen": { "height": 30922 } } ], "vout": [ { "amount": 484778598276, "target": { "key": "44ba20c8a8d8aa0dc51288fb31aeff041c13c644edf9d5653dd027e6e30bf64f" } } ], "extra": [ 1, 107, 79, 247, 54, 222, 137, 51, 205, 57, 223, 81, 79, 239, 72, 31, 149, 178, 11, 37, 4, 244, 8, 30, 78, 37, 79, 222, 184, 157, 99, 205, 138, 2, 17, 0, 0, 0, 172, 172, 52, 191, 158, 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