Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9d8812f19f0196231b7d6b34593007ad28c2cdc2ea6ea6c462aa2a1e31d6cd

Tx prefix hash: a4f8a92e7064aa83fbfeedaf1bb3397192950a62f486d95c5066d10fcb881707
Tx public key: 0b42ca75002051fd20aac7f639525ec3464f88c63564a534f0233301bbc6fce2
Timestamp: 1581474303 Timestamp [UCT]: 2020-02-12 02:25:03 Age [y:d:h:m:s]: 04:290:16:09:15
Block: 63133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099888 RingCT/type: yes/0
Extra: 010b42ca75002051fd20aac7f639525ec3464f88c63564a534f0233301bbc6fce202110000000103d36d11000000000000000000

1 output(s) for total of 379.153419361000 dcy

stealth address amount amount idx
00: 45a1582d3e195f7154982047644a26fad1797cddc9f3e0e5d36749eba8f2d5e3 379.153419361000 116421 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": 63143, "vin": [ { "gen": { "height": 63133 } } ], "vout": [ { "amount": 379153419361, "target": { "key": "45a1582d3e195f7154982047644a26fad1797cddc9f3e0e5d36749eba8f2d5e3" } } ], "extra": [ 1, 11, 66, 202, 117, 0, 32, 81, 253, 32, 170, 199, 246, 57, 82, 94, 195, 70, 79, 136, 198, 53, 100, 165, 52, 240, 35, 51, 1, 187, 198, 252, 226, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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