Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47625db13acfc7abc352cac7fab2e1eff0152e1db20a633cb4ad36548ffb8910

Tx prefix hash: d38db10b42dd8156adcaea273b8bf09a242c702b30fc168f5b3ad1584b570294
Tx public key: ebc7fdc6a503b37e4f41935d93076c318abf4f67bc72ead2535f745ca273736c
Timestamp: 1736446749 Timestamp [UCT]: 2025-01-09 18:19:09 Age [y:d:h:m:s]: 00:078:15:16:37
Block: 1193767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55979 RingCT/type: yes/0
Extra: 01ebc7fdc6a503b37e4f41935d93076c318abf4f67bc72ead2535f745ca273736c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42db074a3f79f958f504d2265aae369d246adcb11833a07c4ba1394a1816f73e 0.600000000000 1680332 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": 1193777, "vin": [ { "gen": { "height": 1193767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42db074a3f79f958f504d2265aae369d246adcb11833a07c4ba1394a1816f73e" } } ], "extra": [ 1, 235, 199, 253, 198, 165, 3, 179, 126, 79, 65, 147, 93, 147, 7, 108, 49, 138, 191, 79, 103, 188, 114, 234, 210, 83, 95, 116, 92, 162, 115, 115, 108, 2, 17, 0, 0, 0, 2, 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