Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec8b74cf3ff9e685c5b2c97b793207ab4b63abecaf008f8da5540b9f7a640f80

Tx prefix hash: cae6cf9c35d98129209a279bbedd149eb0ba18e275bbf3f20fdc60d6fa34b64f
Tx public key: f0d24eabd88ffbada17ef3408389f940523f4104021ab0eb89b45e7e9d9e48c7
Timestamp: 1706770356 Timestamp [UCT]: 2024-02-01 06:52:36 Age [y:d:h:m:s]: 01:281:02:42:38
Block: 947858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459702 RingCT/type: yes/0
Extra: 01f0d24eabd88ffbada17ef3408389f940523f4104021ab0eb89b45e7e9d9e48c702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f2c3158ab107d5e5f0fc1e889238acdd2f0fe23a92d138b80e4df85d8ad6804 0.600000000000 1406216 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": 947868, "vin": [ { "gen": { "height": 947858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f2c3158ab107d5e5f0fc1e889238acdd2f0fe23a92d138b80e4df85d8ad6804" } } ], "extra": [ 1, 240, 210, 78, 171, 216, 143, 251, 173, 161, 126, 243, 64, 131, 137, 249, 64, 82, 63, 65, 4, 2, 26, 176, 235, 137, 180, 94, 126, 157, 158, 72, 199, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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