Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55809486c31f18363b44b81b4ec9ecaa0017af0a6d02366d17135020af7dd96c

Tx prefix hash: 15622d90c6f1869a8a81fe4436386907fcc4b72342ab82f9525373e630fd8fbd
Tx public key: 25b34d975e8ec5e2fd9d713235d6aa6c331cd6dff53665935654387b0581b084
Timestamp: 1714989708 Timestamp [UCT]: 2024-05-06 10:01:48 Age [y:d:h:m:s]: 00:296:00:05:00
Block: 1016017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211560 RingCT/type: yes/0
Extra: 0125b34d975e8ec5e2fd9d713235d6aa6c331cd6dff53665935654387b0581b0840211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02c9e22d9942c3a4ee07ba366d3588fafa5c83b7cad4d1c8a781a6e0bfdf8306 0.600000000000 1479480 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": 1016027, "vin": [ { "gen": { "height": 1016017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02c9e22d9942c3a4ee07ba366d3588fafa5c83b7cad4d1c8a781a6e0bfdf8306" } } ], "extra": [ 1, 37, 179, 77, 151, 94, 142, 197, 226, 253, 157, 113, 50, 53, 214, 170, 108, 51, 28, 214, 223, 245, 54, 101, 147, 86, 84, 56, 123, 5, 129, 176, 132, 2, 17, 0, 0, 0, 7, 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