Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f17d6953fe2ba60805d26fc3bc2f1d3d235101720ce2efe74b8f73cf721ef1

Tx prefix hash: 442c4e52b464efb98ab98f6700a85c997c285f9e98c2b50208e8e8933731aa02
Tx public key: e6eccee005de372aac068ba2fd2a4dbf4265e683c6114d7a627ff5dea7fd7287
Timestamp: 1612831317 Timestamp [UCT]: 2021-02-09 00:41:57 Age [y:d:h:m:s]: 03:290:10:44:51
Block: 194882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 966484 RingCT/type: yes/0
Extra: 01e6eccee005de372aac068ba2fd2a4dbf4265e683c6114d7a627ff5dea7fd72870211000001b490ce5c0f000000000000000000

1 output(s) for total of 138.763634067000 dcy

stealth address amount amount idx
00: 774e3bcda395acdd3bd478fe0722bc1000ed606c0b90961934db99f41e0bd4ca 138.763634067000 396226 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": 194892, "vin": [ { "gen": { "height": 194882 } } ], "vout": [ { "amount": 138763634067, "target": { "key": "774e3bcda395acdd3bd478fe0722bc1000ed606c0b90961934db99f41e0bd4ca" } } ], "extra": [ 1, 230, 236, 206, 224, 5, 222, 55, 42, 172, 6, 139, 162, 253, 42, 77, 191, 66, 101, 230, 131, 198, 17, 77, 122, 98, 127, 245, 222, 167, 253, 114, 135, 2, 17, 0, 0, 1, 180, 144, 206, 92, 15, 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