← previous blocknext block →recent activity
Analyzing
Block #104,876,441
18 transactions · 16 stateful · 2026-09-14 23:19:42 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,876,441 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w211w012w113w315w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a73ae2…2e95
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xad586e22…b48b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xed00498d…8bd5
0x34b655…2a6f
4 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
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
6 conflicts on slot 0xc0a73ae2a1…182e95
Audit this contract →
← previous block·next block →recent activity