Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a31b77c6a87422b5e67d79908cef4d3980eff8daf35c3caef241aed0250307e

Tx prefix hash: 41168bf61e8ee017c1a47333177972cffb189adcf12d081c89740d6d167d6388
Tx public key: 51e9004bcf4eb2a174fccd8217b8c0a785a264062fc96226c9c592ca523ce461
Timestamp: 1747758153 Timestamp [UTC]: 2025-05-20 16:22:33 Age [y:d:h:m:s]: 01:180:05:13:48
Block: 1287149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392774 RingCT/type: yes/0
Extra: 0151e9004bcf4eb2a174fccd8217b8c0a785a264062fc96226c9c592ca523ce46102110000000e1f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 803a7b4b4bb4b4a20f1c77643bd668f123677468243f9c37b3a7387df55b5192 0.000600000000 1774616 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": 1287159, "vin": [ { "gen": { "height": 1287149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803a7b4b4bb4b4a20f1c77643bd668f123677468243f9c37b3a7387df55b5192" } } ], "extra": [ 1, 81, 233, 0, 75, 207, 78, 178, 161, 116, 252, 205, 130, 23, 184, 192, 167, 133, 162, 100, 6, 47, 201, 98, 38, 201, 197, 146, 202, 82, 60, 228, 97, 2, 17, 0, 0, 0, 14, 31, 144, 81, 122, 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: