Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c35e2b9958bdb66d04a1b5a9de0d6a0f0f36f6f695991acd243b87e87a0242a

Tx prefix hash: 99e33e4a18c49cc7c392a4968b20e8f2dd682d03abe3b7865440950ebfbe082d
Tx public key: 0f3cefd4f85969c8936b42decb66409027886426400d2a59d150d0ccb712dceb
Timestamp: 1698518834 Timestamp [UCT]: 2023-10-28 18:47:14 Age [y:d:h:m:s]: 01:220:09:39:13
Block: 879682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418561 RingCT/type: yes/0
Extra: 010f3cefd4f85969c8936b42decb66409027886426400d2a59d150d0ccb712dceb021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.746875776000 dcy

stealth address amount amount idx
00: 2c130308ebd05fab0f948128614ce73f1046637a358ef3947eac2e3d7a373e53 0.746875776000 1335216 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": 879692, "vin": [ { "gen": { "height": 879682 } } ], "vout": [ { "amount": 746875776, "target": { "key": "2c130308ebd05fab0f948128614ce73f1046637a358ef3947eac2e3d7a373e53" } } ], "extra": [ 1, 15, 60, 239, 212, 248, 89, 105, 200, 147, 107, 66, 222, 203, 102, 64, 144, 39, 136, 100, 38, 64, 13, 42, 89, 209, 80, 208, 204, 183, 18, 220, 235, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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