Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1309074309669dbfcf86e1a5437251cd4be73f56f6fed26002c67082a18d14c0

Tx prefix hash: d737ff4f4fd370c226a52726cf671ebf8ce802f942a89a317e8eddfe20f9767b
Tx public key: 458493174004cdf91909ae7f2e051150b930e3e92be0adcab1d6f263e90ac9b2
Timestamp: 1760353729 Timestamp [UCT]: 2025-10-13 11:08:49 Age [y:d:h:m:s]: 00:039:03:54:37
Block: 1388987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28033 RingCT/type: yes/0
Extra: 01458493174004cdf91909ae7f2e051150b930e3e92be0adcab1d6f263e90ac9b2021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa534eb0ae4024faec54c6b348c8b34209aa44297294ccdc9f9d2323f9950fc9 0.600000000000 1877210 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": 1388997, "vin": [ { "gen": { "height": 1388987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa534eb0ae4024faec54c6b348c8b34209aa44297294ccdc9f9d2323f9950fc9" } } ], "extra": [ 1, 69, 132, 147, 23, 64, 4, 205, 249, 25, 9, 174, 127, 46, 5, 17, 80, 185, 48, 227, 233, 43, 224, 173, 202, 177, 214, 242, 99, 233, 10, 201, 178, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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