← previous blocknext block →recent activity
Analyzing
Block #96,266,166
21 transactions · 20 stateful · 2026-08-15 17:43:32 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,266,166 · 21 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
1w03w04w16w07w08w19w010w211w113w014w315w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x75e42ac3…fb18
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x94228f63…f3e1
0x34b655…2a6f
4 touches
1 conflict
0xa6848351…2238
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
3 conflicts on slot 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity