Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13a4bc56e91821469ee317202f1faf33ba27de015eb528ba50017dbce3bdc6a

Tx prefix hash: ea0dcf87de73f8cafdccdf66c4ef48cebeca5dca9a240cbd2b9c36ea1ce4329e
Tx public key: 497db32127ff99b0d778a6875c4aad5ca0bf4a8e6cd4c66be1dbb6cc7220f76f
Timestamp: 1730511033 Timestamp [UCT]: 2024-11-02 01:30:33 Age [y:d:h:m:s]: 01:033:01:32:13
Block: 1144613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282097 RingCT/type: yes/0
Extra: 01497db32127ff99b0d778a6875c4aad5ca0bf4a8e6cd4c66be1dbb6cc7220f76f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39f624ab92aac7d77a411c4a8aec40637152a836e358f7c52c67ec358851c6c3 0.600000000000 1628876 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": 1144623, "vin": [ { "gen": { "height": 1144613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39f624ab92aac7d77a411c4a8aec40637152a836e358f7c52c67ec358851c6c3" } } ], "extra": [ 1, 73, 125, 179, 33, 39, 255, 153, 176, 215, 120, 166, 135, 92, 74, 173, 92, 160, 191, 74, 142, 108, 212, 198, 107, 225, 219, 182, 204, 114, 32, 247, 111, 2, 17, 0, 0, 0, 4, 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