Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6b917df4256150dbfbe1862f9fb9a4ace49b2ade1af91d39e649fdc0183976

Tx prefix hash: 3313e2dc9deddeb34ae9187dbc8c7314123384b38c5dd63c21967293fadb012b
Tx public key: c2a4bdd27e8342d32427d86d030e21964bca0baee5e6efd776a89f2f8d512f25
Timestamp: 1728377079 Timestamp [UCT]: 2024-10-08 08:44:39 Age [y:d:h:m:s]: 00:046:18:53:23
Block: 1127008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33414 RingCT/type: yes/0
Extra: 01c2a4bdd27e8342d32427d86d030e21964bca0baee5e6efd776a89f2f8d512f25021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fac1661dc47e588c5e4e660ad71a4c9294c121c452e7350ab7b17f99983d14d 0.600000000000 1609807 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": 1127018, "vin": [ { "gen": { "height": 1127008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fac1661dc47e588c5e4e660ad71a4c9294c121c452e7350ab7b17f99983d14d" } } ], "extra": [ 1, 194, 164, 189, 210, 126, 131, 66, 211, 36, 39, 216, 109, 3, 14, 33, 150, 75, 202, 11, 174, 229, 230, 239, 215, 118, 168, 159, 47, 141, 81, 47, 37, 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