← previous blocknext block →recent activity
Analyzing
Block #96,281,340
11 transactions · 7 stateful · 2026-08-15 18:59:51 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,281,340 · 11 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
2w03w14w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe00608f8…edc2
0x34b655…2a6f
4 touches
1 conflict
0x3f5b9011…1bae
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x60d732ff…3b8a
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
1 conflict on slot 0xe00608f80d…a6edc2
Audit this contract →
← previous block·next block →recent activity