Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2027ed94292761efcd0ff8c6ed62b8aa19825bc36a4c55a0bfb62caa9927655

Tx prefix hash: c0da070a8aabe43114536adb4f5daf3f2f5332f9c7f37c767bb4720a1e06b05f
Tx public key: f3e415751771b9ca36d26636293ff0e279bbe9913a79a7a3b542217e8791566d
Timestamp: 1756178086 Timestamp [UCT]: 2025-08-26 03:14:46 Age [y:d:h:m:s]: 00:159:17:29:49
Block: 1354562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114019 RingCT/type: yes/0
Extra: 01f3e415751771b9ca36d26636293ff0e279bbe9913a79a7a3b542217e8791566d021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c92738d8bb24a71f2c9e4d4a4e99429201a1b03b8790cfd8e0f27e2ba1264b2 0.600000000000 1842551 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": 1354572, "vin": [ { "gen": { "height": 1354562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c92738d8bb24a71f2c9e4d4a4e99429201a1b03b8790cfd8e0f27e2ba1264b2" } } ], "extra": [ 1, 243, 228, 21, 117, 23, 113, 185, 202, 54, 210, 102, 54, 41, 63, 240, 226, 121, 187, 233, 145, 58, 121, 167, 163, 181, 66, 33, 126, 135, 145, 86, 109, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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