← previous blocknext block →recent activity
Analyzing
Block #99,106,507
24 transactions · 22 stateful · 2026-08-25 17:49:07 UTC
Parallelism
83/100
Blocked
14%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,106,507 · 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
5w017w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf039e2f8…3d8a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa2882400…8dcd
0x34b655…2a6f
4 touches
1 conflict
0xbc2de485…918d
0x34b655…2a6f
4 touches
1 conflict
0x37c0660b…e0bf
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
2 touches
0 conflicts
0xa05dafe7…aff6
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
3 conflicts on slot 0xf039e2f8da…b73d8a
Audit this contract →
← previous block·next block →recent activity