Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48d3ec897724b4fa33411ce71d7af19d6e4e9ad49eda2e875d8dae84fb2fbcb

Tx prefix hash: f262ee2c347f68b86aeeed5e6c936ad1508532f3dbe9a6aa48af5354a4da27af
Tx public key: b35d4ac4704648f3017eacf58c6142880257c2c69ff1de733aaa05d597e2e282
Timestamp: 1693997975 Timestamp [UCT]: 2023-09-06 10:59:35 Age [y:d:h:m:s]: 01:139:16:33:35
Block: 842168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361132 RingCT/type: yes/0
Extra: 01b35d4ac4704648f3017eacf58c6142880257c2c69ff1de733aaa05d597e2e282021100000003faf35c9c000000000000000000

1 output(s) for total of 0.994369703000 dcy

stealth address amount amount idx
00: 99c9507be6c6c02ab256e9e6e86bf77fbc6daa9670884067301f59774d1110db 0.994369703000 1295262 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": 842178, "vin": [ { "gen": { "height": 842168 } } ], "vout": [ { "amount": 994369703, "target": { "key": "99c9507be6c6c02ab256e9e6e86bf77fbc6daa9670884067301f59774d1110db" } } ], "extra": [ 1, 179, 93, 74, 196, 112, 70, 72, 243, 1, 126, 172, 245, 140, 97, 66, 136, 2, 87, 194, 198, 159, 241, 222, 115, 58, 170, 5, 213, 151, 226, 226, 130, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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