← previous blocknext block →recent activity
Analyzing
Block #104,033,588
20 transactions · 20 stateful · 2026-09-12 00:05:08 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,033,588 · 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
1w02w13w04w15w07w110w211w012w113w014w215w117w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3250389…8774
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0x850f88e5…d8ce
0x34b655…2a6f
4 touches
1 conflict
0x8f482d8d…ee6c
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
6 conflicts on slot 0xa325038957…7f8774
Audit this contract →
← previous block·next block →recent activity