Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de424bfab856b77c351546a1f39f0708272c5d439041bfdb7e54ec593db9885c

Tx prefix hash: 0cda6fd38d44ba2e8821f9c510174f51cbe9493c62c728096e55ed60b7a09211
Tx public key: 39adc5995b8dca5a1a3ba65170f07189d31ae0a0eec38d981f1b24cac9a74099
Timestamp: 1735073018 Timestamp [UCT]: 2024-12-24 20:43:38 Age [y:d:h:m:s]: 00:099:01:44:00
Block: 1182402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70581 RingCT/type: yes/0
Extra: 0139adc5995b8dca5a1a3ba65170f07189d31ae0a0eec38d981f1b24cac9a740990211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68da74c8e30db9e8f96153d8116793722ca97ed1fab482ec9ec1170d312ab1df 0.600000000000 1668835 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": 1182412, "vin": [ { "gen": { "height": 1182402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68da74c8e30db9e8f96153d8116793722ca97ed1fab482ec9ec1170d312ab1df" } } ], "extra": [ 1, 57, 173, 197, 153, 91, 141, 202, 90, 26, 59, 166, 81, 112, 240, 113, 137, 211, 26, 224, 160, 238, 195, 141, 152, 31, 27, 36, 202, 201, 167, 64, 153, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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