Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32da6b6567058fcfd1f64b50e9358c0b1613e68a2c3c1c0b05d46e4925e7803a

Tx prefix hash: 084ce2e8ab3627e84388d1dda215ee9ac3169197c946e03db8079f41be615890
Tx public key: 7ec094d0f19af0ffe55d9757f0fda3d106d3d25d1521ee1a0acd9d44d8f9ebdc
Timestamp: 1726764478 Timestamp [UCT]: 2024-09-19 16:47:58 Age [y:d:h:m:s]: 00:114:18:09:52
Block: 1113636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82060 RingCT/type: yes/0
Extra: 017ec094d0f19af0ffe55d9757f0fda3d106d3d25d1521ee1a0acd9d44d8f9ebdc021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88d52458e1f6f0d31ba82d75ca42607b3c700fdb080af29c3d81f95fa7c3dcfd 0.600000000000 1593379 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": 1113646, "vin": [ { "gen": { "height": 1113636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88d52458e1f6f0d31ba82d75ca42607b3c700fdb080af29c3d81f95fa7c3dcfd" } } ], "extra": [ 1, 126, 192, 148, 208, 241, 154, 240, 255, 229, 93, 151, 87, 240, 253, 163, 209, 6, 211, 210, 93, 21, 33, 238, 26, 10, 205, 157, 68, 216, 249, 235, 220, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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