Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592f588ffd62e89fb0a08819dea19f3d4138d96bbfdb5c221cfa5bd14393024d

Tx prefix hash: 5b28cc7dda7a86ca101d0a197de4e2779a316ca4ade1067431533a1c4c60e34d
Tx public key: ca6fd4750588e3a4221746ba563a6c9fecdcd9ce2065ff92f7dfcb973b2fe6e8
Timestamp: 1764227027 Timestamp [UCT]: 2025-11-27 07:03:47 Age [y:d:h:m:s]: 00:026:20:36:15
Block: 1421091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19224 RingCT/type: yes/0
Extra: 01ca6fd4750588e3a4221746ba563a6c9fecdcd9ce2065ff92f7dfcb973b2fe6e80211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec11aa1a195064e7143d42612eec6eeb0186a272bbdf89f263d588fb374aac7a 0.600000000000 1909646 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": 1421101, "vin": [ { "gen": { "height": 1421091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec11aa1a195064e7143d42612eec6eeb0186a272bbdf89f263d588fb374aac7a" } } ], "extra": [ 1, 202, 111, 212, 117, 5, 136, 227, 164, 34, 23, 70, 186, 86, 58, 108, 159, 236, 220, 217, 206, 32, 101, 255, 146, 247, 223, 203, 151, 59, 47, 230, 232, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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