Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d86ec3b68ad5dad66a4007d8280a2d7d0b27e1f236da56ec6194e832a689a08f

Tx prefix hash: e5445102f1d6d416646f2cf080ab68330c4096450335897d9acdae58c1d56627
Tx public key: f3f47df5efc6ae0ad1d70887b5f5e837a4528bcfc33e45c5c841e7849007ecad
Timestamp: 1587782221 Timestamp [UCT]: 2020-04-25 02:37:01 Age [y:d:h:m:s]: 05:168:07:28:47
Block: 95568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1290522 RingCT/type: yes/0
Extra: 01f3f47df5efc6ae0ad1d70887b5f5e837a4528bcfc33e45c5c841e7849007ecad0211000000028a2ee0d9000000000000000000

1 output(s) for total of 296.035852607000 dcy

stealth address amount amount idx
00: b0d65657ea2076ce4029dfad8964debaa89d39e124cb0cba411551bc81ae6f0a 296.035852607000 169815 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": 95578, "vin": [ { "gen": { "height": 95568 } } ], "vout": [ { "amount": 296035852607, "target": { "key": "b0d65657ea2076ce4029dfad8964debaa89d39e124cb0cba411551bc81ae6f0a" } } ], "extra": [ 1, 243, 244, 125, 245, 239, 198, 174, 10, 209, 215, 8, 135, 181, 245, 232, 55, 164, 82, 139, 207, 195, 62, 69, 197, 200, 65, 231, 132, 144, 7, 236, 173, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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