← previous blocknext block →recent activity
Analyzing
Block #101,680,048
14 transactions · 12 stateful · 2026-09-03 17:58:00 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,680,048 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w111w312w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8fbc8aa5…8120
0x34b655…2a6f
6 touches
3 conflicts
0xc8d02208…8db3
0x34b655…2a6f
6 touches
3 conflicts
0x2e05467a…e3b3
0x34b655…2a6f
6 touches
3 conflicts
0xcf61f287…3f4e
0x34b655…2a6f
6 touches
3 conflicts
0xd161cd4f…a626
0x34b655…2a6f
6 touches
3 conflicts
0x08f27947…090f
0xd32edf…ff58
5 touches
3 conflicts
0x02372d42…1871
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity