← previous blocknext block →recent activity
Analyzing
Block #106,555,520
14 transactions · 14 stateful · 2026-09-20 20:12:56 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,555,520 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w29w310w411w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7013779…71d5
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0x4a3d16fb…bfcf
0x34b655…2a6f
4 touches
1 conflict
0x5e3bfff1…7e91
0x34b655…2a6f
4 touches
1 conflict
0x7303f0bf…aca8
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
10 conflicts on slot 0xe7013779b8…5671d5
Audit this contract →
← previous block·next block →recent activity