← previous blocknext block →recent activity
Analyzing
Block #107,838,919
20 transactions · 19 stateful · 2026-09-25 07:56:06 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,838,919 · 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
2w05w06w112w113w114w215w316w417w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25144f94…1854
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x5c5965d0…cb12
0x34b655…2a6f
6 touches
3 conflicts
0xa5365492…1f6f
0x34b655…2a6f
4 touches
1 conflict
0xa2c4d203…05b6
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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
10 conflicts on slot 0x25144f94f3…701854
Audit this contract →
← previous block·next block →recent activity