← previous blocknext block →recent activity
Analyzing
Block #104,032,168
18 transactions · 17 stateful · 2026-09-11 23:57:55 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
2.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,032,168 · 18 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
1w02w13w27w08w19w210w311w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd793c15e…7dba
0x34b655…2a6f
18 touches
36 conflicts
0x028594e3…157c
0x34b655…2a6f
18 touches
36 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
16 touches
28 conflicts
0x91b682aa…be5c
0x34b655…2a6f
16 touches
28 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
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
36 conflicts on slot 0xd793c15e21…747dba
Audit this contract →
← previous block·next block →recent activity