Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38df68eb6b5beb93866c08613364e80a3287afe2870c2303fe34a3f073371a3f

Tx prefix hash: f23db713c9465f2b8bfb819db10f4c46198f640688faef2da90bd53f24731b96
Tx public key: 7ded1d101aae1eaddfbe3445d99fb3c1ee1f360de432923f9bbbd2d758a84cb7
Timestamp: 1739249023 Timestamp [UCT]: 2025-02-11 04:43:43 Age [y:d:h:m:s]: 00:328:21:23:30
Block: 1216708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232881 RingCT/type: yes/0
Extra: 017ded1d101aae1eaddfbe3445d99fb3c1ee1f360de432923f9bbbd2d758a84cb702110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 664c8ce191992434f02c4c693ea9e70a243b8960c3af90fbd943297773896dbe 0.600000000000 1703515 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": 1216718, "vin": [ { "gen": { "height": 1216708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "664c8ce191992434f02c4c693ea9e70a243b8960c3af90fbd943297773896dbe" } } ], "extra": [ 1, 125, 237, 29, 16, 26, 174, 30, 173, 223, 190, 52, 69, 217, 159, 179, 193, 238, 31, 54, 13, 228, 50, 146, 63, 155, 187, 210, 215, 88, 168, 76, 183, 2, 17, 0, 0, 0, 12, 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