← previous blocknext block →recent activity
Analyzing
Block #96,114,834
13 transactions · 13 stateful · 2026-08-15 05:02:20 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,114,834 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x1c582483…7b74
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x2734e00b…9b4f
0x3bd359…433a
2 touches
0 conflicts
0x9bcb6bb0…5b5f
0x3bd359…433a
2 touches
0 conflicts
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
1 conflict on slot 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity