Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48fe2f5fa815e493c5ff37c7ab733791bca8072e30a73de969e105b55c5ac030

Tx prefix hash: 9a6c4a6c8fb5f28be6b33b1c15fde63546018bd669749cc4e1aa349fd6412169
Tx public key: bf044a2325df5a601362b26e3b515cabdd9f0008b059cc50c7a653b734a5af54
Timestamp: 1582292778 Timestamp [UCT]: 2020-02-21 13:46:18 Age [y:d:h:m:s]: 05:081:13:55:07
Block: 69533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211507 RingCT/type: yes/0
Extra: 01bf044a2325df5a601362b26e3b515cabdd9f0008b059cc50c7a653b734a5af540211000000027adf42d3000000000000000000

1 output(s) for total of 361.084720033000 dcy

stealth address amount amount idx
00: 3c2337d7e816857cc22853d842b24d01811156c9fc854305c78f822afd1fe843 361.084720033000 128256 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": 69543, "vin": [ { "gen": { "height": 69533 } } ], "vout": [ { "amount": 361084720033, "target": { "key": "3c2337d7e816857cc22853d842b24d01811156c9fc854305c78f822afd1fe843" } } ], "extra": [ 1, 191, 4, 74, 35, 37, 223, 90, 96, 19, 98, 178, 110, 59, 81, 92, 171, 221, 159, 0, 8, 176, 89, 204, 80, 199, 166, 83, 183, 52, 165, 175, 84, 2, 17, 0, 0, 0, 2, 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