Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52142ef66d8a72ebfb9a3b57c93e4a9e910633457f3ceae70851f9680f49873c

Tx prefix hash: e456265ac10e77b32aa58defacabf3265afc5d298ee573b6d4ebd3947ae3bf29
Tx public key: fb14f7aab211da69d99db6e6104923453da90dc4051b3c6540655e2d0740e150
Timestamp: 1774246754 Timestamp [UTC]: 2026-03-23 06:19:14 Age [y:d:h:m:s]: 00:243:18:37:24
Block: 1503879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179615 RingCT/type: yes/0
Extra: 01fb14f7aab211da69d99db6e6104923453da90dc4051b3c6540655e2d0740e150021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdfe1465151065f2b42c6e0d04014e3d725a703a1a7470ade494929ea59b07fa 0.000600000000 1993593 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 dinastycoin-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": 1503889, "vin": [ { "gen": { "height": 1503879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdfe1465151065f2b42c6e0d04014e3d725a703a1a7470ade494929ea59b07fa" } } ], "extra": [ 1, 251, 20, 247, 170, 178, 17, 218, 105, 217, 157, 182, 230, 16, 73, 35, 69, 61, 169, 13, 196, 5, 27, 60, 101, 64, 101, 94, 45, 7, 64, 225, 80, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: