← previous blocknext block →recent activity
Analyzing
Block #106,470,976
19 transactions · 17 stateful · 2026-09-20 13:07:26 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,470,976 · 19 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
1w05w17w210w211w312w413w514w616w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47755f1b…bc75
0x34b655…2a6f
14 touches
21 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
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
21 conflicts on slot 0x47755f1b60…1fbc75
Audit this contract →
← previous block·next block →recent activity