Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d88b08913640d087b1276f013a56213f6ef5b49ccbde123b796c41cec6e6839

Tx prefix hash: 5c66c60f20a9ccce646cdc0d099513679554dd1217ce1d5217580a2610a78672
Tx public key: 89f269855186087d1e2e1ce9dbec69dfe5f4001507c4d75a427e1fbf337ad6b5
Timestamp: 1735058661 Timestamp [UCT]: 2024-12-24 16:44:21 Age [y:d:h:m:s]: 00:106:10:46:42
Block: 1182291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75858 RingCT/type: yes/0
Extra: 0189f269855186087d1e2e1ce9dbec69dfe5f4001507c4d75a427e1fbf337ad6b50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88b7ae6cd2ff276f635e4cd7a572d08fcc804d908317bd58c52edf0c806ec6f 0.600000000000 1668724 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": 1182301, "vin": [ { "gen": { "height": 1182291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88b7ae6cd2ff276f635e4cd7a572d08fcc804d908317bd58c52edf0c806ec6f" } } ], "extra": [ 1, 137, 242, 105, 133, 81, 134, 8, 125, 30, 46, 28, 233, 219, 236, 105, 223, 229, 244, 0, 21, 7, 196, 215, 90, 66, 126, 31, 191, 51, 122, 214, 181, 2, 17, 0, 0, 0, 2, 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