← previous blocknext block →recent activity
Analyzing
Block #99,249,662
27 transactions · 21 stateful · 2026-08-26 05:49:26 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,249,662 · 27 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
2w04w16w07w18w29w312w014w117w118w119w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x126c10ea…a328
0x34b655…2a6f
4 touches
1 conflict
0x259f891b…c9fd
0x34b655…2a6f
4 touches
1 conflict
0x2691869a…dd4c
0x34b655…2a6f
4 touches
1 conflict
0x4fa72287…fa62
0x34b655…2a6f
4 touches
1 conflict
0x5f46663c…b4c2
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity