Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e06ab76336885452f9c4d60f0b4af64b9f51b4cfdb7f732fe4dc851b29bc01

Tx prefix hash: a3c5a40298bcb734faae27a8b5a28a0340dfd381a2997be7b52d786c286eca12
Tx public key: f237609d42136271c8f8449d42621b53852e5ed42af64e71dcb7bbda5a4e0903
Timestamp: 1755787863 Timestamp [UCT]: 2025-08-21 14:51:03 Age [y:d:h:m:s]: 00:135:10:55:36
Block: 1351350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96795 RingCT/type: yes/0
Extra: 01f237609d42136271c8f8449d42621b53852e5ed42af64e71dcb7bbda5a4e0903021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4626e14cfb25e2442b373ac24584c08505fa5bcefbfcfd262090bae5f6dc7532 0.600000000000 1839301 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": 1351360, "vin": [ { "gen": { "height": 1351350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4626e14cfb25e2442b373ac24584c08505fa5bcefbfcfd262090bae5f6dc7532" } } ], "extra": [ 1, 242, 55, 96, 157, 66, 19, 98, 113, 200, 248, 68, 157, 66, 98, 27, 83, 133, 46, 94, 212, 42, 246, 78, 113, 220, 183, 187, 218, 90, 78, 9, 3, 2, 17, 0, 0, 0, 2, 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