Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363ab9fd2a9ac0ced9ecb10624022fa5ae635817f6b31e773dd14040e5a55941

Tx prefix hash: 7dd3b1baacfb1bfcd02fa0635ed2990e6524a0aa4c17c0f2e223f156343ac15e
Tx public key: f449912f22169b6107210f226b4f98a17aa7115008a7daa26b49abc5f6d4a4f1
Timestamp: 1765868357 Timestamp [UCT]: 2025-12-16 06:59:17 Age [y:d:h:m:s]: 00:047:04:56:40
Block: 1434691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33616 RingCT/type: yes/0
Extra: 01f449912f22169b6107210f226b4f98a17aa7115008a7daa26b49abc5f6d4a4f102110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7555204a851b46a80e08ad358a38d937c3ae1af01476183b693684c87456ba3 0.600000000000 1923482 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": 1434701, "vin": [ { "gen": { "height": 1434691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7555204a851b46a80e08ad358a38d937c3ae1af01476183b693684c87456ba3" } } ], "extra": [ 1, 244, 73, 145, 47, 34, 22, 155, 97, 7, 33, 15, 34, 107, 79, 152, 161, 122, 167, 17, 80, 8, 167, 218, 162, 107, 73, 171, 197, 246, 212, 164, 241, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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