Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c39e5571ca0d21b3e29f32d9df8166f7eb2f1eab669c57905173ba804750c7d

Tx prefix hash: 173f50f710f794e8d2e85e97cfff56692c0f9e150e995f93a01cf6720733f48d
Tx public key: 70d3b264b99fc2c9a1a4c10aae412880c9f34f50cf45fcfe39c0a48d7299145c
Timestamp: 1734432512 Timestamp [UCT]: 2024-12-17 10:48:32 Age [y:d:h:m:s]: 00:326:05:00:05
Block: 1177119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230626 RingCT/type: yes/0
Extra: 0170d3b264b99fc2c9a1a4c10aae412880c9f34f50cf45fcfe39c0a48d7299145c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 593a894aeb4552e9b996109685fac47e84571ff215d3f387411a34033f107a51 0.600000000000 1663484 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": 1177129, "vin": [ { "gen": { "height": 1177119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "593a894aeb4552e9b996109685fac47e84571ff215d3f387411a34033f107a51" } } ], "extra": [ 1, 112, 211, 178, 100, 185, 159, 194, 201, 161, 164, 193, 10, 174, 65, 40, 128, 201, 243, 79, 80, 207, 69, 252, 254, 57, 192, 164, 141, 114, 153, 20, 92, 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