Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4817fe119f0713df318da0eac8a68d2c37d7f098210954b49a688bac9759e091

Tx prefix hash: d4f8cc4663da8df8035e99251b5e0638b1e80f8976a357719d72f16ccb152405
Tx public key: c243148e3339adcfbb4fb096c154249e0b643d4abd21711adccdbbc6e56bfaf3
Timestamp: 1734742967 Timestamp [UCT]: 2024-12-21 01:02:47 Age [y:d:h:m:s]: 00:092:07:40:57
Block: 1179688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65745 RingCT/type: yes/0
Extra: 01c243148e3339adcfbb4fb096c154249e0b643d4abd21711adccdbbc6e56bfaf30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18388f9ede62a3d4e49b8f51e632515d75954f1bd33ab955162194bd236b3cb 0.600000000000 1666087 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": 1179698, "vin": [ { "gen": { "height": 1179688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18388f9ede62a3d4e49b8f51e632515d75954f1bd33ab955162194bd236b3cb" } } ], "extra": [ 1, 194, 67, 20, 142, 51, 57, 173, 207, 187, 79, 176, 150, 193, 84, 36, 158, 11, 100, 61, 74, 189, 33, 113, 26, 220, 205, 187, 198, 229, 107, 250, 243, 2, 17, 0, 0, 0, 4, 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