← previous blocknext block →recent activity
Analyzing
Block #105,601,134
21 transactions · 19 stateful · 2026-09-17 12:07:01 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,601,134 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w211w112w213w315w117w418w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x232de52b…9edb
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x92f41d1f…4258
0xa6afd3…d132
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity