Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f9b8f9439627e2f12a58aa0ce2a013d4ae87fd103fb6ed95f4a49d9eeca5615

Tx prefix hash: 82bc99ae576de4a5838fe4a971244b57b5ecdb235327c4b27bce234798cf27ff
Tx public key: cef0c488faef5deed7261b3cbc7c534f4c3466641169fd54a744343150948196
Timestamp: 1724355068 Timestamp [UCT]: 2024-08-22 19:31:08 Age [y:d:h:m:s]: 00:226:13:13:18
Block: 1093672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161769 RingCT/type: yes/0
Extra: 01cef0c488faef5deed7261b3cbc7c534f4c3466641169fd54a744343150948196021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a04e0687c7afbe94782bbd57c69bf43e8e6217440fcaa336c99d9f28b531f31 0.600000000000 1568661 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": 1093682, "vin": [ { "gen": { "height": 1093672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a04e0687c7afbe94782bbd57c69bf43e8e6217440fcaa336c99d9f28b531f31" } } ], "extra": [ 1, 206, 240, 196, 136, 250, 239, 93, 238, 215, 38, 27, 60, 188, 124, 83, 79, 76, 52, 102, 100, 17, 105, 253, 84, 167, 68, 52, 49, 80, 148, 129, 150, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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