Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a609adfcd635be42b8e5b11fe7ea1c4b1501e3f7db98b375e6402d36b895ebbb

Tx prefix hash: 6d89a8988dfdedcbbf09e4ddffde627778da65085e9103b81216bb048ab23cf5
Tx public key: 68ecd7d01ac174b3e6526e3c63d3b8c733f97d4103802700fd0344ad8dad2a4d
Timestamp: 1719293366 Timestamp [UCT]: 2024-06-25 05:29:26 Age [y:d:h:m:s]: 01:189:09:27:11
Block: 1051689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393979 RingCT/type: yes/0
Extra: 0168ecd7d01ac174b3e6526e3c63d3b8c733f97d4103802700fd0344ad8dad2a4d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cdcc89e7cdaf2371a86da16c977e17cbc3fd94ff8e17289f7aa5da860e82ddc 0.600000000000 1522004 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": 1051699, "vin": [ { "gen": { "height": 1051689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cdcc89e7cdaf2371a86da16c977e17cbc3fd94ff8e17289f7aa5da860e82ddc" } } ], "extra": [ 1, 104, 236, 215, 208, 26, 193, 116, 179, 230, 82, 110, 60, 99, 211, 184, 199, 51, 249, 125, 65, 3, 128, 39, 0, 253, 3, 68, 173, 141, 173, 42, 77, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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