Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a3acb256a5e84e2075febc496ad5bd8ffd7b30fbac31e4abaa6766a64e04d7

Tx prefix hash: e728413c589754e0855c7eb0626844e9f284f9550f73532213cb153e670a3751
Tx public key: 86a9abc98634b9fba6968e597a84f6bfb3d15d3b22b2989afd4117cbd8a2d4a6
Timestamp: 1735172719 Timestamp [UCT]: 2024-12-26 00:25:19 Age [y:d:h:m:s]: 00:096:04:04:18
Block: 1183223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68513 RingCT/type: yes/0
Extra: 0186a9abc98634b9fba6968e597a84f6bfb3d15d3b22b2989afd4117cbd8a2d4a6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0dd323b408ca055de442b0e7e8bbb7a5676b18a1bac915976284e66468657c3 0.600000000000 1669664 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": 1183233, "vin": [ { "gen": { "height": 1183223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0dd323b408ca055de442b0e7e8bbb7a5676b18a1bac915976284e66468657c3" } } ], "extra": [ 1, 134, 169, 171, 201, 134, 52, 185, 251, 166, 150, 142, 89, 122, 132, 246, 191, 179, 209, 93, 59, 34, 178, 152, 154, 253, 65, 23, 203, 216, 162, 212, 166, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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