← previous blocknext block →recent activity
Analyzing
Block #104,161,182
16 transactions · 14 stateful · 2026-09-12 10:54:28 UTC
Parallelism
44/100
Blocked
57%
Avg conflicts / tx
1.81
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,161,182 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w610w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x5e28e919…c782
0x34b655…2a6f
8 touches
6 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
6 touches
3 conflicts
0xce2f0b6e…0e05
0x34b655…2a6f
6 touches
3 conflicts
0xe01158fd…f982
0x1b6862…e19c
4 touches
1 conflict
0x0da71bf6…4d35
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
21 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity