Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d07cac7052668a4bdbca7b15834c1742796ea9356299bbbaf0eb336f96d2de9

Tx prefix hash: 1b715e45d6c2de176e7ad6affbd93a531a02f0d483f0d4913dec7d3552a2a051
Tx public key: ff396c4b4749707bcc0fc3aac60623a70f4cf115ad66f8938d9cdc5bab394b8c
Timestamp: 1675367163 Timestamp [UCT]: 2023-02-02 19:46:03 Age [y:d:h:m:s]: 02:023:11:44:39
Block: 688406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538372 RingCT/type: yes/0
Extra: 01ff396c4b4749707bcc0fc3aac60623a70f4cf115ad66f8938d9cdc5bab394b8c0211000000015029cbac000000000000000000

1 output(s) for total of 3.213846139000 dcy

stealth address amount amount idx
00: a65a4160a3bee8cb8398a5d11e6d26220063e94354450acb2b196e831742f4c3 3.213846139000 1131022 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": 688416, "vin": [ { "gen": { "height": 688406 } } ], "vout": [ { "amount": 3213846139, "target": { "key": "a65a4160a3bee8cb8398a5d11e6d26220063e94354450acb2b196e831742f4c3" } } ], "extra": [ 1, 255, 57, 108, 75, 71, 73, 112, 123, 204, 15, 195, 170, 198, 6, 35, 167, 15, 76, 241, 21, 173, 102, 248, 147, 141, 156, 220, 91, 171, 57, 75, 140, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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