Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737bea5c16f44e207f15d14e87831ddf24686f8d722a8dd626cd1b3e3a121485

Tx prefix hash: da83f6e8c30caed475eabada80f8f0d79b4e8a89672131504a51fb8cfe0d40f4
Tx public key: 3ecdbe36d439c3fa5bd4aae80101f09a655d2d82862335aed04250a6bbd01944
Timestamp: 1582342570 Timestamp [UCT]: 2020-02-22 03:36:10 Age [y:d:h:m:s]: 04:310:14:15:26
Block: 70063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114387 RingCT/type: yes/0
Extra: 013ecdbe36d439c3fa5bd4aae80101f09a655d2d82862335aed04250a6bbd01944021100000001026b59f3000000000000000000

1 output(s) for total of 359.662637847000 dcy

stealth address amount amount idx
00: 58962db60382aa6fdf22c3acca288e02cc2bd765323e03e444ca07073495b122 359.662637847000 129271 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": 70073, "vin": [ { "gen": { "height": 70063 } } ], "vout": [ { "amount": 359662637847, "target": { "key": "58962db60382aa6fdf22c3acca288e02cc2bd765323e03e444ca07073495b122" } } ], "extra": [ 1, 62, 205, 190, 54, 212, 57, 195, 250, 91, 212, 170, 232, 1, 1, 240, 154, 101, 93, 45, 130, 134, 35, 53, 174, 208, 66, 80, 166, 187, 208, 25, 68, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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