← previous blocknext block →recent activity
Analyzing
Block #99,291,125
40 transactions · 37 stateful · 2026-08-26 09:18:06 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,291,125 · 40 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w511w613w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
14 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x8488f10f…9355
0x2b46c0…1669
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity