← previous blocknext block →recent activity
Analyzing
Block #94,999,802
17 transactions · 16 stateful · 2026-08-11 07:17:58 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,999,802 · 17 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
2w03w14w25w38w09w110w411w512w615w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x01774b56…13e1
0x34b655…2a6f
4 touches
1 conflict
0x0ae69c4a…0c0f
0x34b655…2a6f
4 touches
1 conflict
0x388c3a1b…2749
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
15 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity