← previous blocknext block →recent activity
Analyzing
Block #99,937,826
36 transactions · 25 stateful · 2026-08-28 15:47:08 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,937,826 · 36 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
1w07w110w012w016w217w018w119w120w221w122w128w332w033w134w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6538fb…2b3f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaaf5bec3…8aad
0xd32edf…ff58
5 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
4 touches
1 conflict
0x78375f3b…b4cc
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 0xdd6538fbaf…632b3f
Audit this contract →
← previous block·next block →recent activity