Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73b6537eb7b25887ecee08d2423e14e642d41e684789cd4e931a68c801d2601c

Tx prefix hash: d15a0edea35efeb38e702a257b380bb065c61d8f798e586842352c847940ecd4
Tx public key: 90f469a9773b1d8164b6cb3273504751f35db9cdc7d934da69be56e9e4a9c4a2
Timestamp: 1744975058 Timestamp [UTC]: 2025-04-18 11:17:38 Age [y:d:h:m:s]: 01:030:23:03:33
Block: 1264106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274083 RingCT/type: yes/0
Extra: 0190f469a9773b1d8164b6cb3273504751f35db9cdc7d934da69be56e9e4a9c4a2021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 314858c2b61e195e42809e730e67b88613fc7721ce3ef983894910910a03300a 0.000600000000 1751299 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": 1264116, "vin": [ { "gen": { "height": 1264106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314858c2b61e195e42809e730e67b88613fc7721ce3ef983894910910a03300a" } } ], "extra": [ 1, 144, 244, 105, 169, 119, 59, 29, 129, 100, 182, 203, 50, 115, 80, 71, 81, 243, 93, 185, 205, 199, 217, 52, 218, 105, 190, 86, 233, 228, 169, 196, 162, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: