← previous blocknext block →recent activity
Analyzing
Block #106,004,884
26 transactions · 23 stateful · 2026-09-18 22:01:39 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,004,884 · 26 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
1w02w03w14w05w19w011w112w214w320w222w123w224w025w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1e9a3afd…a6e5
0x34b655…2a6f
4 touches
1 conflict
0x3f152ba8…cea6
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x419f4b7d…6f21
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
3 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity