Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d326fe570c8c54593e65c03b7a7fe2065d0a8c3d888d92ece0fabd378f17c5b8

Tx prefix hash: 18b379fdccdff0fdceee42a4db82e5d28b5abb78c4cd3df6b896094d2794c65a
Tx public key: 0e896fcea0c0604a298aee95f3fa773ad28824137917f4bf43d601ac0461bfc6
Timestamp: 1705001720 Timestamp [UCT]: 2024-01-11 19:35:20 Age [y:d:h:m:s]: 01:088:13:40:38
Block: 933195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324415 RingCT/type: yes/0
Extra: 010e896fcea0c0604a298aee95f3fa773ad28824137917f4bf43d601ac0461bfc60211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f07c08bb3da5529fc60f235e572bdf251de17221ae54dbd820dc47454ba4f6e0 0.600000000000 1391155 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": 933205, "vin": [ { "gen": { "height": 933195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f07c08bb3da5529fc60f235e572bdf251de17221ae54dbd820dc47454ba4f6e0" } } ], "extra": [ 1, 14, 137, 111, 206, 160, 192, 96, 74, 41, 138, 238, 149, 243, 250, 119, 58, 210, 136, 36, 19, 121, 23, 244, 191, 67, 214, 1, 172, 4, 97, 191, 198, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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