← previous blocknext block →recent activity
Analyzing
Block #109,228,503
25 transactions · 19 stateful · 2026-09-30 04:37:29 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,228,503 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w28w310w411w512w513w614w723w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4064a8f…d9a7
0x34b655…2a6f
8 touches
6 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
8 touches
6 conflicts
0xb74eb6a8…a225
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe3ae2b3f…309e
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
4 touches
1 conflict
0xdc1ee9ba…027d
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 0xf4064a8ff9…82d9a7
Audit this contract →
← previous block·next block →recent activity