← previous blocknext block →recent activity
Analyzing
Block #103,212,716
13 transactions · 12 stateful · 2026-09-09 03:02:11 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,212,716 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf84a6…09e4
0x34b655…2a6f
4 touches
1 conflict
0x6455c121…f808
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe6b16d23…9ee9
0x34b655…2a6f
4 touches
1 conflict
0x03725241…6314
0x34b655…2a6f
2 touches
0 conflicts
0x03f08d80…0661
0x34b655…2a6f
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x04acfef0…16d8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x18cf84a64e…8b09e4
Audit this contract →
← previous block·next block →recent activity