Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6570b04ae4a2a918e309f761bf72df5e1f99d284a2165208ad2e818383bce49

Tx prefix hash: 735a40c54d1fe648abcc5414b54a332dc829a810779001f75934f6afc4bc7740
Tx public key: c3828ac850d9c996182023aa57419140d63f53d4d5ed6ae00e75aa6efd48f006
Timestamp: 1732499960 Timestamp [UCT]: 2024-11-25 01:59:20 Age [y:d:h:m:s]: 00:136:04:47:49
Block: 1161082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97167 RingCT/type: yes/0
Extra: 01c3828ac850d9c996182023aa57419140d63f53d4d5ed6ae00e75aa6efd48f0060211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c59e3561c47a788ee10f5e416c5a08bd71b64ae1c897cdcdf9dcd151ade6389 0.600000000000 1646733 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": 1161092, "vin": [ { "gen": { "height": 1161082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c59e3561c47a788ee10f5e416c5a08bd71b64ae1c897cdcdf9dcd151ade6389" } } ], "extra": [ 1, 195, 130, 138, 200, 80, 217, 201, 150, 24, 32, 35, 170, 87, 65, 145, 64, 214, 63, 83, 212, 213, 237, 106, 224, 14, 117, 170, 110, 253, 72, 240, 6, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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