← previous blocknext block →recent activity
Analyzing
Block #104,810,994
24 transactions · 22 stateful · 2026-09-14 17:49:23 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,810,994 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w211w312w415w216w322w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1002d20f…b67a
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x059e0ac0…0267
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x976812c5…36fb
0x34b655…2a6f
4 touches
1 conflict
0xdba7d06b…cb59
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 0x1002d20f1b…08b67a
Audit this contract →
← previous block·next block →recent activity