Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40273729fa864119d3fd232759c84f92c6b1e08b71e5a07d220b642f24fc2a3d

Tx prefix hash: edf72ec741a268644bad09bdccf8c003a80a3f3e8036880cd92da64e6e8892e5
Tx public key: d4e6a33233629952d312d18d2ff088fd3e47ca45e58bc279b3f286d767f7556b
Timestamp: 1716170043 Timestamp [UCT]: 2024-05-20 01:54:03 Age [y:d:h:m:s]: 00:282:07:59:25
Block: 1025805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201768 RingCT/type: yes/0
Extra: 01d4e6a33233629952d312d18d2ff088fd3e47ca45e58bc279b3f286d767f7556b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b82a86d685c90fe323a687b91bee92a6a2ac08d8de40f3428adc5510a3ae5cd 0.600000000000 1492538 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": 1025815, "vin": [ { "gen": { "height": 1025805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b82a86d685c90fe323a687b91bee92a6a2ac08d8de40f3428adc5510a3ae5cd" } } ], "extra": [ 1, 212, 230, 163, 50, 51, 98, 153, 82, 211, 18, 209, 141, 47, 240, 136, 253, 62, 71, 202, 69, 229, 139, 194, 121, 179, 242, 134, 215, 103, 247, 85, 107, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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