Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49047d49638d263d2784855b34a10e34968a21cac89f4e760524f0b73643062

Tx prefix hash: fceb73b953817a61ae661083bae2d10aa1b492a3cf6ba49baee5117fb5c1b2cb
Tx public key: ca8805c0af5a6ce8ec72eccab2bc27da485a6dc70c5e078d1d0ade0e37846a80
Timestamp: 1703580161 Timestamp [UCT]: 2023-12-26 08:42:41 Age [y:d:h:m:s]: 01:316:22:08:50
Block: 921423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485333 RingCT/type: yes/0
Extra: 01ca8805c0af5a6ce8ec72eccab2bc27da485a6dc70c5e078d1d0ade0e37846a80021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e45c124910734c1a387340b906c1a4808dade483d418a521473ee61bd2f971a6 0.600000000000 1379111 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": 921433, "vin": [ { "gen": { "height": 921423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e45c124910734c1a387340b906c1a4808dade483d418a521473ee61bd2f971a6" } } ], "extra": [ 1, 202, 136, 5, 192, 175, 90, 108, 232, 236, 114, 236, 202, 178, 188, 39, 218, 72, 90, 109, 199, 12, 94, 7, 141, 29, 10, 222, 14, 55, 132, 106, 128, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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