← previous blocknext block →recent activity
Analyzing
Block #99,099,562
24 transactions · 24 stateful · 2026-08-25 17:14:11 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,099,562 · 24 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
4w05w16w110w211w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d22c394…c125
0x34b655…2a6f
6 touches
3 conflicts
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x4147c716…7412
0x34b655…2a6f
4 touches
1 conflict
0x61b2753d…4ce6
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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
3 conflicts on slot 0x9d22c394fb…48c125
Audit this contract →
← previous block·next block →recent activity