Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997bff8f5703ad40003d73971550f6f4ceb057a05d7a36b1d8140558f545c94c

Tx prefix hash: 4d34cd4a20bb194dba8f46e24a4b7ac51149de46913156a40d27c77fffe8434e
Tx public key: fd338dac82c6e5815598891d8f1b1c2150c33509c81c3800f860f2dcd5b63283
Timestamp: 1726792220 Timestamp [UCT]: 2024-09-20 00:30:20 Age [y:d:h:m:s]: 00:196:15:52:52
Block: 1113861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140380 RingCT/type: yes/0
Extra: 01fd338dac82c6e5815598891d8f1b1c2150c33509c81c3800f860f2dcd5b63283021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4cbf3841c2ac3a589b3d4a736884bccded7e84d4217be4044c3f53619557d8f 0.600000000000 1593658 of 15

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": 1113871, "vin": [ { "gen": { "height": 1113861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4cbf3841c2ac3a589b3d4a736884bccded7e84d4217be4044c3f53619557d8f" } } ], "extra": [ 1, 253, 51, 141, 172, 130, 198, 229, 129, 85, 152, 137, 29, 143, 27, 28, 33, 80, 195, 53, 9, 200, 28, 56, 0, 248, 96, 242, 220, 213, 182, 50, 131, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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