Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38e99730ff0f1b4b9aec30e72b5251ac8192742903433eb8ca0a528ee8946da

Tx prefix hash: 5a3cc50207a507edbe08faa0bb7d98c61e099f63bee3ff8ada1b1a3441d0791d
Tx public key: 5682abd3dbdce9672a83bb6c00fcce39d9f8ce2394b37bbd564fd0250af50f53
Timestamp: 1697369488 Timestamp [UCT]: 2023-10-15 11:31:28 Age [y:d:h:m:s]: 02:069:12:02:49
Block: 870144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569336 RingCT/type: yes/0
Extra: 015682abd3dbdce9672a83bb6c00fcce39d9f8ce2394b37bbd564fd0250af50f53021100000004faf35c9c000000000000000000

1 output(s) for total of 0.803251862000 dcy

stealth address amount amount idx
00: 02af2168f75d27f9b8f32e5add3b71baff0715c09254248827fb508cd6ca987b 0.803251862000 1325017 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": 870154, "vin": [ { "gen": { "height": 870144 } } ], "vout": [ { "amount": 803251862, "target": { "key": "02af2168f75d27f9b8f32e5add3b71baff0715c09254248827fb508cd6ca987b" } } ], "extra": [ 1, 86, 130, 171, 211, 219, 220, 233, 103, 42, 131, 187, 108, 0, 252, 206, 57, 217, 248, 206, 35, 148, 179, 123, 189, 86, 79, 208, 37, 10, 245, 15, 83, 2, 17, 0, 0, 0, 4, 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