Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aacc94cdc468fc5060bec2498c420a516caac63233b4d58301e8c34ead7e7cca

Tx prefix hash: 2b4248a5714f4f1cd9aca1a86e26974b620cab582a86564dbc347b14e364dd7d
Tx public key: 211058fc01544eaf4f216c30cca7c9cbd1f3efff6ea1f252c035a76684ebf8b3
Timestamp: 1709368852 Timestamp [UCT]: 2024-03-02 08:40:52 Age [y:d:h:m:s]: 01:108:08:31:52
Block: 969423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338370 RingCT/type: yes/0
Extra: 01211058fc01544eaf4f216c30cca7c9cbd1f3efff6ea1f252c035a76684ebf8b30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb36f790d38ba8d0b5371efbdbb3b6cf2931ac751396065ae810271cf39f806f 0.600000000000 1429252 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": 969433, "vin": [ { "gen": { "height": 969423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb36f790d38ba8d0b5371efbdbb3b6cf2931ac751396065ae810271cf39f806f" } } ], "extra": [ 1, 33, 16, 88, 252, 1, 84, 78, 175, 79, 33, 108, 48, 204, 167, 201, 203, 209, 243, 239, 255, 110, 161, 242, 82, 192, 53, 167, 102, 132, 235, 248, 179, 2, 17, 0, 0, 0, 3, 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