← previous blocknext block →recent activity
Analyzing
Block #101,993,360
16 transactions · 14 stateful · 2026-09-04 20:18:17 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,993,360 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w27w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b7fbba…64de
0x34b655…2a6f
6 touches
3 conflicts
0xadc848ee…5cb2
0x34b655…2a6f
6 touches
3 conflicts
0x5dd033b6…34b5
0x34b655…2a6f
6 touches
3 conflicts
0xf139b130…d132
0x34b655…2a6f
6 touches
3 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x2ce2d49e…d187
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1dc71894…1884
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 0x33b7fbba1a…5e64de
Audit this contract →
← previous block·next block →recent activity