Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58e5d0ce530909cc2d438b593601eee547315c214f5b6b2385e60c26d5cc6a48

Tx prefix hash: d73ae87eb1324b87ddbccc96c29aa756a8c6e8f44d1a43c08b2987003a7e7a5c
Tx public key: 023ef9e0c5edbe8e2929139b3d1a3b6ca4fc0799f7290ad7c5ee01442476789b
Timestamp: 1580700830 Timestamp [UCT]: 2020-02-03 03:33:50 Age [y:d:h:m:s]: 04:334:03:45:55
Block: 57619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130096 RingCT/type: yes/0
Extra: 01023ef9e0c5edbe8e2929139b3d1a3b6ca4fc0799f7290ad7c5ee01442476789b021100000001b221b3d1000000000000000000

1 output(s) for total of 395.444150767000 dcy

stealth address amount amount idx
00: 322b6d53373618e78e949a6768a8d56b43317bc78f3d0ad6a35d779e6fe70cd6 395.444150767000 106503 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": 57629, "vin": [ { "gen": { "height": 57619 } } ], "vout": [ { "amount": 395444150767, "target": { "key": "322b6d53373618e78e949a6768a8d56b43317bc78f3d0ad6a35d779e6fe70cd6" } } ], "extra": [ 1, 2, 62, 249, 224, 197, 237, 190, 142, 41, 41, 19, 155, 61, 26, 59, 108, 164, 252, 7, 153, 247, 41, 10, 215, 197, 238, 1, 68, 36, 118, 120, 155, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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