Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4481a356263ef284c61284d9c786cdd827bfbe7aabc9a417711bdf2aaf1fbdfa

Tx prefix hash: 12bf9235d76b48eec3e34a8f5a2972ab0038a03b10f70bbe7e53efb05899054b
Tx public key: eaea5ce9f53ba6185c13272872ba7585f51c9959d741f797889728cf41eedbcc
Timestamp: 1587355130 Timestamp [UCT]: 2020-04-20 03:58:50 Age [y:d:h:m:s]: 05:022:13:21:42
Block: 94412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186321 RingCT/type: yes/0
Extra: 01eaea5ce9f53ba6185c13272872ba7585f51c9959d741f797889728cf41eedbcc0211000000f839be35fb000000000000000000

1 output(s) for total of 298.658322060000 dcy

stealth address amount amount idx
00: 0cd24325832b650e28aaf78d3f97e7d5b0f7fa07f840cd0d88c32bb4777dbdf9 298.658322060000 167904 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": 94422, "vin": [ { "gen": { "height": 94412 } } ], "vout": [ { "amount": 298658322060, "target": { "key": "0cd24325832b650e28aaf78d3f97e7d5b0f7fa07f840cd0d88c32bb4777dbdf9" } } ], "extra": [ 1, 234, 234, 92, 233, 245, 59, 166, 24, 92, 19, 39, 40, 114, 186, 117, 133, 245, 28, 153, 89, 215, 65, 247, 151, 136, 151, 40, 207, 65, 238, 219, 204, 2, 17, 0, 0, 0, 248, 57, 190, 53, 251, 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