Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4653cb5e84d4c9654533c6666f62bb3fa7e1513f205a68b922a6edf26fb859f1

Tx prefix hash: 0c058c09891f7f68fa9372183786895bc7f341f5b824b7f729be92bca4cb5148
Tx public key: 3add6ce812cce442fb6ddeaadeb1103dffbccb66290ea3e23b376670d009d752
Timestamp: 1693271480 Timestamp [UCT]: 2023-08-29 01:11:20 Age [y:d:h:m:s]: 01:224:05:38:57
Block: 836143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421385 RingCT/type: yes/0
Extra: 013add6ce812cce442fb6ddeaadeb1103dffbccb66290ea3e23b376670d009d7520211000000024b8f5122000000000000000000

1 output(s) for total of 1.041145002000 dcy

stealth address amount amount idx
00: 6adb5a7707ec76ae06c56f4cceb283ed5ffef814a4c054b0c00b52f5fdaff342 1.041145002000 1288721 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": 836153, "vin": [ { "gen": { "height": 836143 } } ], "vout": [ { "amount": 1041145002, "target": { "key": "6adb5a7707ec76ae06c56f4cceb283ed5ffef814a4c054b0c00b52f5fdaff342" } } ], "extra": [ 1, 58, 221, 108, 232, 18, 204, 228, 66, 251, 109, 222, 170, 222, 177, 16, 61, 255, 188, 203, 102, 41, 14, 163, 226, 59, 55, 102, 112, 208, 9, 215, 82, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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