← previous blocknext block →recent activity
Analyzing
Block #99,607,740
14 transactions · 13 stateful · 2026-08-27 11:57:12 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,607,740 · 14 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
1w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe226a0be…c046
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x206c55db…94ea
0x34b655…2a6f
4 touches
1 conflict
0x0203a60f…d0bd
0x34b655…2a6f
2 touches
0 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
2 touches
0 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
2 touches
0 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
2 touches
0 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
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 0xe226a0be4d…4bc046
Audit this contract →
← previous block·next block →recent activity