← previous blocknext block →recent activity
Analyzing
Block #106,955,613
29 transactions · 25 stateful · 2026-09-22 05:47:39 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,955,613 · 29 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
1w04w09w110w211w113w314w415w527w428w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e546ea4…d63c
0x34b655…2a6f
12 touches
15 conflicts
0x4ebd9eec…d5c3
0x34b655…2a6f
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xa140ac77…1f0c
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x21e79ad8…c5db
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
15 conflicts on slot 0x1e546ea4be…7fd63c
Audit this contract →
← previous block·next block →recent activity