Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57b5368c3f0d9f10cf9c4573c859a2a0ccbfaa4ee2ac3944b4d86a6cbe21ae4

Tx prefix hash: 96d17e58cdb4601e3c20cf5deddc9f81b99a54640306654c7b4adbc8a721a9af
Tx public key: e0cca15adc5142c2ad270f65326e1ef80bf6dbcc16ac1dd63aaeeaf8debc9ca1
Timestamp: 1731077344 Timestamp [UCT]: 2024-11-08 14:49:04 Age [y:d:h:m:s]: 00:051:03:15:42
Block: 1149313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36573 RingCT/type: yes/0
Extra: 01e0cca15adc5142c2ad270f65326e1ef80bf6dbcc16ac1dd63aaeeaf8debc9ca10211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8088e1db376957c95439d58e6fefcfb944b1092a99b2b4c5f55a5ccd7d4faa78 0.600000000000 1634362 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": 1149323, "vin": [ { "gen": { "height": 1149313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8088e1db376957c95439d58e6fefcfb944b1092a99b2b4c5f55a5ccd7d4faa78" } } ], "extra": [ 1, 224, 204, 161, 90, 220, 81, 66, 194, 173, 39, 15, 101, 50, 110, 30, 248, 11, 246, 219, 204, 22, 172, 29, 214, 58, 174, 234, 248, 222, 188, 156, 161, 2, 17, 0, 0, 0, 6, 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