Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56a11286521fa3402b7b8a59ea5b77d3800ded04e39281493535eb76cda38cd5

Tx prefix hash: aa8e679769096e2a50b2eacdaeb5e45f662e2fc7de7a3c86ea2c75139b58f20a
Tx public key: 7c6dffa41bd3b29b08ec11a95f48910ed77e5ceb08f0c0d1f12d19a4178fa509
Timestamp: 1714132094 Timestamp [UCT]: 2024-04-26 11:48:14 Age [y:d:h:m:s]: 01:049:18:53:26
Block: 1008905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296460 RingCT/type: yes/0
Extra: 017c6dffa41bd3b29b08ec11a95f48910ed77e5ceb08f0c0d1f12d19a4178fa5090211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7129a67c506fd032875f68599d3aabc63222a984251b9789dbabd4816cdcf4 0.600000000000 1470413 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": 1008915, "vin": [ { "gen": { "height": 1008905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7129a67c506fd032875f68599d3aabc63222a984251b9789dbabd4816cdcf4" } } ], "extra": [ 1, 124, 109, 255, 164, 27, 211, 178, 155, 8, 236, 17, 169, 95, 72, 145, 14, 215, 126, 92, 235, 8, 240, 192, 209, 241, 45, 25, 164, 23, 143, 165, 9, 2, 17, 0, 0, 0, 6, 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