Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48d4f376fb8cf094b256aa1ade45e20dfb6f117e60779255bec3959156a89686

Tx prefix hash: afe3a94c403c9e366d5118ecd12730c716692d590a3512357aa55d57f777cd7e
Tx public key: 18a470e895b4be6f093b5cfd4042dd223a630e9ea6ee82f0d23c76124102577e
Timestamp: 1696600376 Timestamp [UCT]: 2023-10-06 13:52:56 Age [y:d:h:m:s]: 01:092:12:37:59
Block: 863769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327389 RingCT/type: yes/0
Extra: 0118a470e895b4be6f093b5cfd4042dd223a630e9ea6ee82f0d23c76124102577e021100000012faf35c9c000000000000000000

1 output(s) for total of 0.843285770000 dcy

stealth address amount amount idx
00: a6130f24253f690a770375fc6f74d0c78ce32fef51706dc79144d2e735c5306c 0.843285770000 1318259 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": 863779, "vin": [ { "gen": { "height": 863769 } } ], "vout": [ { "amount": 843285770, "target": { "key": "a6130f24253f690a770375fc6f74d0c78ce32fef51706dc79144d2e735c5306c" } } ], "extra": [ 1, 24, 164, 112, 232, 149, 180, 190, 111, 9, 59, 92, 253, 64, 66, 221, 34, 58, 99, 14, 158, 166, 238, 130, 240, 210, 60, 118, 18, 65, 2, 87, 126, 2, 17, 0, 0, 0, 18, 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