← previous blocknext block →recent activity
Analyzing
Block #101,682,489
20 transactions · 18 stateful · 2026-09-03 18:10:17 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,682,489 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w110w013w014w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xbf6a171a…7d71
0xd32edf…ff58
7 touches
6 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity