Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0084b7c10ed1f2f72285d2376ae5a5cbb057c84cbf2cca8107c74a46e88a4342

Tx prefix hash: 51cca4b7621ad7d1420431e9d7e13d709286822ad6851b160fe3c3444dd7e6c1
Tx public key: 2f083b1d629dc10a0a608357162624a946f95c7eb8ad52ffb67d56436c5aa2bb
Timestamp: 1751056183 Timestamp [UCT]: 2025-06-27 20:29:43 Age [y:d:h:m:s]: 00:146:01:16:43
Block: 1314058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102453 RingCT/type: yes/0
Extra: 012f083b1d629dc10a0a608357162624a946f95c7eb8ad52ffb67d56436c5aa2bb021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165a1730d96bd38fd614ba0cba1aee079c34a391b8a481e9f14e63461172c24a 0.600000000000 1801703 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": 1314068, "vin": [ { "gen": { "height": 1314058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165a1730d96bd38fd614ba0cba1aee079c34a391b8a481e9f14e63461172c24a" } } ], "extra": [ 1, 47, 8, 59, 29, 98, 157, 193, 10, 10, 96, 131, 87, 22, 38, 36, 169, 70, 249, 92, 126, 184, 173, 82, 255, 182, 125, 86, 67, 108, 90, 162, 187, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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