Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2bc01caab519a9ea7151f2fb2c8c8e2381dcd69864da1f266d1ded9dca56638

Tx prefix hash: 9d803afd06879bf57504206af706a9eaabef75b398b27250e35a029270eb9b73
Tx public key: 0653f97bebf881ded2d66e3cd46744f6288e4f9373c1475ac970ea1448d6769c
Timestamp: 1581824019 Timestamp [UCT]: 2020-02-16 03:33:39 Age [y:d:h:m:s]: 05:007:06:55:12
Block: 65983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158019 RingCT/type: yes/0
Extra: 010653f97bebf881ded2d66e3cd46744f6288e4f9373c1475ac970ea1448d6769c0211000000017adf42d3000000000000000000

1 output(s) for total of 370.998146351000 dcy

stealth address amount amount idx
00: a3f6d393d2fffd83a164c8e1bdd074d8b8fb60a8a30cf843cf4ee41cb75ce25e 370.998146351000 121620 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": 65993, "vin": [ { "gen": { "height": 65983 } } ], "vout": [ { "amount": 370998146351, "target": { "key": "a3f6d393d2fffd83a164c8e1bdd074d8b8fb60a8a30cf843cf4ee41cb75ce25e" } } ], "extra": [ 1, 6, 83, 249, 123, 235, 248, 129, 222, 210, 214, 110, 60, 212, 103, 68, 246, 40, 142, 79, 147, 115, 193, 71, 90, 201, 112, 234, 20, 72, 214, 118, 156, 2, 17, 0, 0, 0, 1, 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