← previous blocknext block →recent activity
Analyzing
Block #102,211,101
20 transactions · 18 stateful · 2026-09-05 14:41:57 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,211,101 · 20 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
1w02w13w24w05w16w27w39w010w115w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec07cf7…c0c9
0x34b655…2a6f
8 touches
6 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
8 touches
6 conflicts
0x5746581b…0cb1
0x34b655…2a6f
8 touches
6 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x15d9c27d…5638
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
6 conflicts on slot 0x0ec07cf780…9cc0c9
Audit this contract →
← previous block·next block →recent activity