← previous blocknext block →recent activity
Analyzing
Block #95,715,249
19 transactions · 19 stateful · 2026-08-13 19:32:00 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,715,249 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w010w411w513w014w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6fd055a9…34a5
0x34b655…2a6f
4 touches
1 conflict
0x9408df94…6750
0x34b655…2a6f
4 touches
1 conflict
0x9e5adfc8…489d
0x34b655…2a6f
4 touches
1 conflict
0xa13535db…1162
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity