Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691afeb183e121a3f4b7d17c3f47614c415ae7d81ba8f20d6dec18f387dcda10

Tx prefix hash: a5764f72febc6e7c8ef321180b73e2d0d13e446896620268ba79e601432a180f
Tx public key: 0340470a97440b0b4b364341c0c2081f609cbe54082e08c983e302ba4b62f56b
Timestamp: 1703613021 Timestamp [UCT]: 2023-12-26 17:50:21 Age [y:d:h:m:s]: 01:331:06:31:39
Block: 921695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495610 RingCT/type: yes/0
Extra: 010340470a97440b0b4b364341c0c2081f609cbe54082e08c983e302ba4b62f56b021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a2f1fc9edc826dea059907821e2e122defbb118563e73a3c2591a7737878991 0.600000000000 1379387 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": 921705, "vin": [ { "gen": { "height": 921695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a2f1fc9edc826dea059907821e2e122defbb118563e73a3c2591a7737878991" } } ], "extra": [ 1, 3, 64, 71, 10, 151, 68, 11, 11, 75, 54, 67, 65, 192, 194, 8, 31, 96, 156, 190, 84, 8, 46, 8, 201, 131, 227, 2, 186, 75, 98, 245, 107, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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