Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a117c29bb3df0490219a700ac3fbce9df084a1f0278f1dfa1536531cbda9585

Tx prefix hash: 0bff1bef4fbafa972439a8e9713b2c904088fdbaf4edf18f9f0256e65e13d091
Tx public key: 1f7fe289648ed3e28f65260535e085abe2f6f17ec970058249f622ed6ca2b893
Timestamp: 1713247496 Timestamp [UCT]: 2024-04-16 06:04:56 Age [y:d:h:m:s]: 00:158:16:43:12
Block: 1001555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113695 RingCT/type: yes/0
Extra: 011f7fe289648ed3e28f65260535e085abe2f6f17ec970058249f622ed6ca2b8930211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd9b425e5efa7d0a4fdd02f25d38e555ce63f44daa249a446ff7dddc7ac257d5 0.600000000000 1462061 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": 1001565, "vin": [ { "gen": { "height": 1001555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd9b425e5efa7d0a4fdd02f25d38e555ce63f44daa249a446ff7dddc7ac257d5" } } ], "extra": [ 1, 31, 127, 226, 137, 100, 142, 211, 226, 143, 101, 38, 5, 53, 224, 133, 171, 226, 246, 241, 126, 201, 112, 5, 130, 73, 246, 34, 237, 108, 162, 184, 147, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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