Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64254551e4adf2bc99dd83dfc38f2ac9455c3545ca04e80a1e4227646fade340

Tx prefix hash: 5055eef0d605b97350a06bfee0d65836fd298443a4aa8c3bf780961897c23563
Tx public key: 2f715fe38a19e4446a9ad3d19843a75ee553d9d45b9afff598b64601e6d97a38
Timestamp: 1746976218 Timestamp [UTC]: 2025-05-11 15:10:18 Age [y:d:h:m:s]: 01:100:03:33:37
Block: 1280670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336265 RingCT/type: yes/0
Extra: 012f715fe38a19e4446a9ad3d19843a75ee553d9d45b9afff598b64601e6d97a380211000000039f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5619d650ae874e0f9f4fa86ae915dbec8582ea1bd0bf2dd6c25ac3474b66f8d6 0.000600000000 1768059 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": 1280680, "vin": [ { "gen": { "height": 1280670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5619d650ae874e0f9f4fa86ae915dbec8582ea1bd0bf2dd6c25ac3474b66f8d6" } } ], "extra": [ 1, 47, 113, 95, 227, 138, 25, 228, 68, 106, 154, 211, 209, 152, 67, 167, 94, 229, 83, 217, 212, 91, 154, 255, 245, 152, 182, 70, 1, 230, 217, 122, 56, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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: