Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f04491f8e0152ceed7bf7180a9f9c580274c8cc7c222179aeee743e2c5d95c8

Tx prefix hash: 7ea33596d7094bcec23c5fbd65e597739cb51d61b13306bd66291f960a4ca361
Tx public key: a87e855ffe301560bd632e59f1719c97c46f154eec4168a0e27cfe1ba0d1f6b8
Timestamp: 1747178725 Timestamp [UTC]: 2025-05-13 23:25:25 Age [y:d:h:m:s]: 01:190:13:48:59
Block: 1282349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400367 RingCT/type: yes/0
Extra: 01a87e855ffe301560bd632e59f1719c97c46f154eec4168a0e27cfe1ba0d1f6b80211000000059f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65b1b16f994185848c68e3c4c8765300368df8916eed6d6d964e94fddc07d889 0.000600000000 1769756 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": 1282359, "vin": [ { "gen": { "height": 1282349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b1b16f994185848c68e3c4c8765300368df8916eed6d6d964e94fddc07d889" } } ], "extra": [ 1, 168, 126, 133, 95, 254, 48, 21, 96, 189, 99, 46, 89, 241, 113, 156, 151, 196, 111, 21, 78, 236, 65, 104, 160, 226, 124, 254, 27, 160, 209, 246, 184, 2, 17, 0, 0, 0, 5, 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: