← previous blocknext block →recent activity
Analyzing
Block #99,210,040
20 transactions · 16 stateful · 2026-08-26 02:30:05 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,210,040 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w211w312w413w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdf025ee…1e6c
0x34b655…2a6f
6 touches
3 conflicts
0xfb8cab34…dd97
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbdb4610b…9ed5
0x065c9d…c394
4 touches
1 conflict
0x0d03bddb…6658
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
3 conflicts on slot 0xbdf025eec3…cc1e6c
Audit this contract →
← previous block·next block →recent activity