Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66e564f6f78f6a1b8d86a57c90add1b67429c29eab15ca655ab0e2d1e3e0ae36

Tx prefix hash: f74afc0132adac9b39f1b1791a9374ae9f4b41db0e589f0a3c3f0007df5be359
Tx public key: 0601f88e651ff02f411315989fb6ee8caf697d00133da23ae1f731ae5b1a9c6b
Timestamp: 1729848620 Timestamp [UCT]: 2024-10-25 09:30:20 Age [y:d:h:m:s]: 00:181:04:32:11
Block: 1139162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129313 RingCT/type: yes/0
Extra: 010601f88e651ff02f411315989fb6ee8caf697d00133da23ae1f731ae5b1a9c6b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c508caaf1d53a2e736dcc8e5aba010fb84f364c7e80e09dc866168880b922eb1 0.600000000000 1622931 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": 1139172, "vin": [ { "gen": { "height": 1139162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c508caaf1d53a2e736dcc8e5aba010fb84f364c7e80e09dc866168880b922eb1" } } ], "extra": [ 1, 6, 1, 248, 142, 101, 31, 240, 47, 65, 19, 21, 152, 159, 182, 238, 140, 175, 105, 125, 0, 19, 61, 162, 58, 225, 247, 49, 174, 91, 26, 156, 107, 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