Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f34fc1e00a072e0b52d1a9e081a15a4a66057e50bcb963ed771248edcd5385f

Tx prefix hash: e283974eb597a84b37b612693d047feaf346be05a5d2fd24a5ed6d4d681fe806
Tx public key: 2aa4a98cd6ae21c611a0765e1a222a6684f0d3bdbf2791a0014e24439240684b
Timestamp: 1754330142 Timestamp [UCT]: 2025-08-04 17:55:42 Age [y:d:h:m:s]: 00:150:00:31:58
Block: 1340245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106249 RingCT/type: yes/0
Extra: 012aa4a98cd6ae21c611a0765e1a222a6684f0d3bdbf2791a0014e24439240684b021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da344c15c579f2572139a433cc88f2686341d7a27d13f0e8d95c94e09d650dba 0.600000000000 1828062 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": 1340255, "vin": [ { "gen": { "height": 1340245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da344c15c579f2572139a433cc88f2686341d7a27d13f0e8d95c94e09d650dba" } } ], "extra": [ 1, 42, 164, 169, 140, 214, 174, 33, 198, 17, 160, 118, 94, 26, 34, 42, 102, 132, 240, 211, 189, 191, 39, 145, 160, 1, 78, 36, 67, 146, 64, 104, 75, 2, 17, 0, 0, 0, 5, 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