Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 128d338c53583a6ec4b8b3f0e9307a7ff1bc8b7d44829daee2f0469ddce57fb3

Tx prefix hash: bf33cb87bbe29480bb2a6b2eb7feb5bf908dc443597b2f00dce833374dbc25dc
Tx public key: 1cdc5b9853cc59858266d39195ce56cd6a3a8dfb3a32498bb2c9a54c11c97813
Timestamp: 1581474627 Timestamp [UCT]: 2020-02-12 02:30:27 Age [y:d:h:m:s]: 05:094:01:06:08
Block: 63160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220023 RingCT/type: yes/0
Extra: 011cdc5b9853cc59858266d39195ce56cd6a3a8dfb3a32498bb2c9a54c11c978130211000000197adf42d3000000000000000000

1 output(s) for total of 379.075323909000 dcy

stealth address amount amount idx
00: 9b1a851ab118b7a3796db4bb9369d62222fa9ffee7f4a1db5a434aed27de14ec 379.075323909000 116466 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": 63170, "vin": [ { "gen": { "height": 63160 } } ], "vout": [ { "amount": 379075323909, "target": { "key": "9b1a851ab118b7a3796db4bb9369d62222fa9ffee7f4a1db5a434aed27de14ec" } } ], "extra": [ 1, 28, 220, 91, 152, 83, 204, 89, 133, 130, 102, 211, 145, 149, 206, 86, 205, 106, 58, 141, 251, 58, 50, 73, 139, 178, 201, 165, 76, 17, 201, 120, 19, 2, 17, 0, 0, 0, 25, 122, 223, 66, 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