Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe232607d1b41183caae00af3b105c7f3c2c46ade737c149bd1f07817c31300

Tx prefix hash: 7868a80c6c52220e41305eb851d325e8c96ec4de98fb16edf835e526f49d41cc
Tx public key: f3f04f90fb545e1eb724b106d78206b6ab4cbdb5e28f3495b8a748da5b66f132
Timestamp: 1703936789 Timestamp [UCT]: 2023-12-30 11:46:29 Age [y:d:h:m:s]: 01:128:09:02:11
Block: 924387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352875 RingCT/type: yes/0
Extra: 01f3f04f90fb545e1eb724b106d78206b6ab4cbdb5e28f3495b8a748da5b66f132021100000003ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84939e14eb7dc6196f0711cb2db6432626017774c004fc06cfb6ea1274dba142 0.600000000000 1382135 of 15

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": 924397, "vin": [ { "gen": { "height": 924387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84939e14eb7dc6196f0711cb2db6432626017774c004fc06cfb6ea1274dba142" } } ], "extra": [ 1, 243, 240, 79, 144, 251, 84, 94, 30, 183, 36, 177, 6, 215, 130, 6, 182, 171, 76, 189, 181, 226, 143, 52, 149, 184, 167, 72, 218, 91, 102, 241, 50, 2, 17, 0, 0, 0, 3, 172, 50, 141, 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