Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e0e611b06599533d3bcf5a9e3915bb76ff05b2e0052c2c04a173362928c7542

Tx prefix hash: 9ee9f7712e907cf8137e02c7d71bd582a944a7086f32f4f23f6c8f8ee309936e
Tx public key: 3fa053d8730a984da1d4944efa9739f19ee7c236a5d4b0663cfdf65f46c3cd2c
Timestamp: 1710366132 Timestamp [UCT]: 2024-03-13 21:42:12 Age [y:d:h:m:s]: 01:093:15:01:16
Block: 977705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327832 RingCT/type: yes/0
Extra: 013fa053d8730a984da1d4944efa9739f19ee7c236a5d4b0663cfdf65f46c3cd2c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f3bfe3905f3d127927bb73c0ac6681ca59ea3b9c8e2432f4dadc4d5dc8efc7 0.600000000000 1437708 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": 977715, "vin": [ { "gen": { "height": 977705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f3bfe3905f3d127927bb73c0ac6681ca59ea3b9c8e2432f4dadc4d5dc8efc7" } } ], "extra": [ 1, 63, 160, 83, 216, 115, 10, 152, 77, 161, 212, 148, 78, 250, 151, 57, 241, 158, 231, 194, 54, 165, 212, 176, 102, 60, 253, 246, 95, 70, 195, 205, 44, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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