Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768f2806f37adc2c4b30d4bd1d3a5137ef9ae6070ddc2f331cd365a3f61e744a

Tx prefix hash: 1a08db6ba5848ae065ec6e8d05cd39aac10adb79610ab3356507c311193c3a48
Tx public key: 566e1d2071b82383ef2ef753fc8c80496ddf4f7229bb403d521dd69bd5786cfe
Timestamp: 1730578582 Timestamp [UCT]: 2024-11-02 20:16:22 Age [y:d:h:m:s]: 00:153:01:12:25
Block: 1145171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109215 RingCT/type: yes/0
Extra: 01566e1d2071b82383ef2ef753fc8c80496ddf4f7229bb403d521dd69bd5786cfe0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 89f64dc73f4bdc8c2ad64977862e43fd0f84d7ba13b639f9a1156d8e7ad33e67 0.600200000000 1629566 of 0

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": 1145181, "vin": [ { "gen": { "height": 1145171 } } ], "vout": [ { "amount": 600200000, "target": { "key": "89f64dc73f4bdc8c2ad64977862e43fd0f84d7ba13b639f9a1156d8e7ad33e67" } } ], "extra": [ 1, 86, 110, 29, 32, 113, 184, 35, 131, 239, 46, 247, 83, 252, 140, 128, 73, 109, 223, 79, 114, 41, 187, 64, 61, 82, 29, 214, 155, 213, 120, 108, 254, 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