Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d43aaf9a667612b35050a096bb4ae918f1c5bdeff6c1906ce14dfc00cafd1b8

Tx prefix hash: cfd65bc6be304c0cfdab52c7ab39382d4424a249846c704be42877d1bc9b0b3b
Tx public key: ea69990cf1dba945c7aedfb511a016e90387316733b659bed8b5e885f874bd86
Timestamp: 1744279255 Timestamp [UTC]: 2025-04-10 10:00:55 Age [y:d:h:m:s]: 01:218:14:49:08
Block: 1258342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420176 RingCT/type: yes/0
Extra: 01ea69990cf1dba945c7aedfb511a016e90387316733b659bed8b5e885f874bd860211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 744eccde7c75bb548125eb271a1e57ec6462feaecc1d1f1db39bccdf91fb2d1d 0.000600000000 1745475 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": 1258352, "vin": [ { "gen": { "height": 1258342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "744eccde7c75bb548125eb271a1e57ec6462feaecc1d1f1db39bccdf91fb2d1d" } } ], "extra": [ 1, 234, 105, 153, 12, 241, 219, 169, 69, 199, 174, 223, 181, 17, 160, 22, 233, 3, 135, 49, 103, 51, 182, 89, 190, 216, 181, 232, 133, 248, 116, 189, 134, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: