Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41471a935c1707daf314d1e233d2478a38e16a8fd5540baae2da1b52b8233b7

Tx prefix hash: c3e3f2e1da8ce917a65880de92bbfe8eecf697f5c248d5ed09743df7bc341640
Tx public key: 6f04040070d4a30ed3f2535e0470387acce5153dc1e89be59ecc3d9afdbaac72
Timestamp: 1734852811 Timestamp [UCT]: 2024-12-22 07:33:31 Age [y:d:h:m:s]: 00:096:14:45:10
Block: 1180592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68816 RingCT/type: yes/0
Extra: 016f04040070d4a30ed3f2535e0470387acce5153dc1e89be59ecc3d9afdbaac720211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e3de3de72383c2c3b43a203f8b997af80711d8c3afdd738f1c9edf4df6a4282 0.600000000000 1667005 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": 1180602, "vin": [ { "gen": { "height": 1180592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e3de3de72383c2c3b43a203f8b997af80711d8c3afdd738f1c9edf4df6a4282" } } ], "extra": [ 1, 111, 4, 4, 0, 112, 212, 163, 14, 211, 242, 83, 94, 4, 112, 56, 122, 204, 229, 21, 61, 193, 232, 155, 229, 158, 204, 61, 154, 253, 186, 172, 114, 2, 17, 0, 0, 0, 1, 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