Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c02cd052cd419f367674cc4831797cffade41d995d87535dd0ae98d9bebe24

Tx prefix hash: 6f68f5c56562e099591a8fea9ee509ca44cac973a08f0dcde34e1e09e66f4487
Tx public key: 7475bb878ba6ac98ba6201296b5a148092b69fb863ce7c1bb25f3f1a79e553db
Timestamp: 1772171422 Timestamp [UTC]: 2026-02-27 05:50:22 Age [y:d:h:m:s]: 00:090:01:02:51
Block: 1486709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58433 RingCT/type: yes/0
Extra: 017475bb878ba6ac98ba6201296b5a148092b69fb863ce7c1bb25f3f1a79e553db021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fae7aa4ee0c0f2257bbb1925c558967a95fe3b172e92d434740c2eae73d5a7d4 0.000600000000 1976167 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": 1486719, "vin": [ { "gen": { "height": 1486709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fae7aa4ee0c0f2257bbb1925c558967a95fe3b172e92d434740c2eae73d5a7d4" } } ], "extra": [ 1, 116, 117, 187, 135, 139, 166, 172, 152, 186, 98, 1, 41, 107, 90, 20, 128, 146, 182, 159, 184, 99, 206, 124, 27, 178, 95, 63, 26, 121, 229, 83, 219, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: