Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3e4c828d0c323ec0b6966b792bbc1648ef737588fb93920f5a9bde553871448

Tx prefix hash: 7b894d2e43116a756daef2e65360e6cff26a8803bee8b5e74b20497041bf19b7
Tx public key: c05d63c4d54ae205ff21e110e53f6fbbd4540eb8716a5eb6537bdcf1fa8b9e97
Timestamp: 1734679064 Timestamp [UCT]: 2024-12-20 07:17:44 Age [y:d:h:m:s]: 00:102:03:08:58
Block: 1179163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72748 RingCT/type: yes/0
Extra: 01c05d63c4d54ae205ff21e110e53f6fbbd4540eb8716a5eb6537bdcf1fa8b9e970211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098bd21212d9bc76c77405706be6225b7a7b5dfc4d5cda4ed34f7fa95be41afc 0.600000000000 1665554 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": 1179173, "vin": [ { "gen": { "height": 1179163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098bd21212d9bc76c77405706be6225b7a7b5dfc4d5cda4ed34f7fa95be41afc" } } ], "extra": [ 1, 192, 93, 99, 196, 213, 74, 226, 5, 255, 33, 225, 16, 229, 63, 111, 187, 212, 84, 14, 184, 113, 106, 94, 182, 83, 123, 220, 241, 250, 139, 158, 151, 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