← previous blocknext block →recent activity
Analyzing
Block #94,915,963
16 transactions · 16 stateful · 2026-08-11 00:16:18 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,915,963 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w29w310w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x9ea0c7a7…f14e
0x34b655…2a6f
6 touches
3 conflicts
0x8f33c0a6…c5eb
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
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
6 conflicts on slot 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity