Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55c0e149c97f505b5d1011a2697461e64545928b4865f746732501847698d964

Tx prefix hash: 97cd76c9d09c948c1535cf10ea95e760104b3920d196f05e6dac0dfa64124e30
Tx public key: bc7a6aa1c515551f222c7de8000be5da14b4dfb58082dab9813b0ea2a530a471
Timestamp: 1577984756 Timestamp [UCT]: 2020-01-02 17:05:56 Age [y:d:h:m:s]: 04:309:02:49:00
Block: 37341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109969 RingCT/type: yes/0
Extra: 01bc7a6aa1c515551f222c7de8000be5da14b4dfb58082dab9813b0ea2a530a4710211000000368a2ee0d9000000000000000000

1 output(s) for total of 461.609371869000 dcy

stealth address amount amount idx
00: 164c5e1cf29b782390c58e9d39db99ac4165c7334d8857855bc40a5983646729 461.609371869000 63343 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": 37351, "vin": [ { "gen": { "height": 37341 } } ], "vout": [ { "amount": 461609371869, "target": { "key": "164c5e1cf29b782390c58e9d39db99ac4165c7334d8857855bc40a5983646729" } } ], "extra": [ 1, 188, 122, 106, 161, 197, 21, 85, 31, 34, 44, 125, 232, 0, 11, 229, 218, 20, 180, 223, 181, 128, 130, 218, 185, 129, 59, 14, 162, 165, 48, 164, 113, 2, 17, 0, 0, 0, 54, 138, 46, 224, 217, 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