Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa9fa95415c0b36054081b1198abf58313f6ee8a893205ffb9aaa26a6b92bb2e

Tx prefix hash: d053ed547592f00735e64505b377d5512fc2a16b9c5212e3b570a3948c887cc7
Tx public key: 1fc11c4a89f3d29143c01b93983201e685a3745f11de81450dc074e1247da132
Timestamp: 1750941359 Timestamp [UTC]: 2025-06-26 12:35:59 Age [y:d:h:m:s]: 01:146:05:46:36
Block: 1313188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368877 RingCT/type: yes/0
Extra: 011fc11c4a89f3d29143c01b93983201e685a3745f11de81450dc074e1247da13202110000000643846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 24fdea3862e7df9a378732b4e8c580930565abb610c5b47e0f279c01329e4700 0.000600000000 1800827 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": 1313198, "vin": [ { "gen": { "height": 1313188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24fdea3862e7df9a378732b4e8c580930565abb610c5b47e0f279c01329e4700" } } ], "extra": [ 1, 31, 193, 28, 74, 137, 243, 210, 145, 67, 192, 27, 147, 152, 50, 1, 230, 133, 163, 116, 95, 17, 222, 129, 69, 13, 192, 116, 225, 36, 125, 161, 50, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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: