← previous blocknext block →recent activity
Analyzing
Block #109,233,692
17 transactions · 14 stateful · 2026-09-30 05:03:35 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,233,692 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w111w012w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7d9ef283…ddd1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1eb07c4e…3db5
0x34b655…2a6f
2 touches
0 conflicts
0x285f2611…cac6
0x34b655…2a6f
2 touches
0 conflicts
0x2ae2f960…4f1d
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x1867b65332…1be61b
Audit this contract →
← previous block·next block →recent activity