← previous blocknext block →recent activity
Analyzing
Block #101,658,335
14 transactions · 11 stateful · 2026-09-03 16:08:46 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,658,335 · 14 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
1w02w16w17w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0980c49…6328
0x34b655…2a6f
8 touches
6 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x14d1bf0e…e09d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0b3a121c…f803
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
6 conflicts on slot 0xc0980c49f3…1f6328
Audit this contract →
← previous block·next block →recent activity