← previous blocknext block →recent activity
Analyzing
Block #96,708,631
17 transactions · 14 stateful · 2026-08-17 06:49:13 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,708,631 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w09w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4a52bb3…68b9
0x34b655…2a6f
4 touches
1 conflict
0xbd3363fd…8d12
0x34b655…2a6f
4 touches
1 conflict
0xc9d54af6…1aaf
0x34b655…2a6f
4 touches
1 conflict
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea3b49a7…24d7
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0xf4a52bb3be…7268b9
Audit this contract →
← previous block·next block →recent activity