← previous blocknext block →recent activity
Analyzing
Block #101,988,473
24 transactions · 19 stateful · 2026-09-04 19:53:29 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,988,473 · 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
1w04w05w16w27w38w117w018w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0f6895c…e428
0x34b655…2a6f
8 touches
6 conflicts
0xa1a01ded…c087
0x34b655…2a6f
8 touches
6 conflicts
0xa62eb46f…89b1
0x34b655…2a6f
8 touches
6 conflicts
0x29a58269…011a
0x34b655…2a6f
8 touches
6 conflicts
0xf7772b49…fc12
0x34b655…2a6f
8 touches
6 conflicts
0x6823c28e…594c
0x34b655…2a6f
8 touches
6 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
8 touches
6 conflicts
0x898a08aa…c855
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xc0f6895c5d…fee428
Audit this contract →
← previous block·next block →recent activity