Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d16882002d68c756adf8bed6db960aa016b00bdb566f8b8c5b99aebc7d8ac0cf

Tx prefix hash: d8043e28bcf1a2f4a9fb58e8ffc63e5beb9e8435e72caf9d66d96d4f1d1a86d9
Tx public key: e365b4b718e76a1b0d3ce5458c6ce0941c22beb8143bfe13cacd3dc4e3440089
Timestamp: 1581091137 Timestamp [UCT]: 2020-02-07 15:58:57 Age [y:d:h:m:s]: 04:284:04:31:49
Block: 60708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094477 RingCT/type: yes/0
Extra: 01e365b4b718e76a1b0d3ce5458c6ce0941c22beb8143bfe13cacd3dc4e344008902110000000156c366d3000000000000000000

1 output(s) for total of 386.233564524000 dcy

stealth address amount amount idx
00: 2d15d4084851cfe929b9b86061f2d7fc8d46669ee6d7921a6d16f1bbc05abcb6 386.233564524000 111762 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": 60718, "vin": [ { "gen": { "height": 60708 } } ], "vout": [ { "amount": 386233564524, "target": { "key": "2d15d4084851cfe929b9b86061f2d7fc8d46669ee6d7921a6d16f1bbc05abcb6" } } ], "extra": [ 1, 227, 101, 180, 183, 24, 231, 106, 27, 13, 60, 229, 69, 140, 108, 224, 148, 28, 34, 190, 184, 20, 59, 254, 19, 202, 205, 61, 196, 227, 68, 0, 137, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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