← previous blocknext block →recent activity
Analyzing
Block #104,205,140
20 transactions · 20 stateful · 2026-09-12 14:37:38 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,205,140 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w011w214w315w416w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8de9d19…455e
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x93aa1b2e…8459
0x34b655…2a6f
8 touches
6 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x32b8461e…99f5
0x34b655…2a6f
6 touches
3 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
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
10 conflicts on slot 0xe8de9d19df…19455e
Audit this contract →
← previous block·next block →recent activity