← previous blocknext block →recent activity
Analyzing
Block #106,539,005
19 transactions · 19 stateful · 2026-09-20 18:49:49 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,539,005 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w111w012w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ac18b8d…0c1c
0x34b655…2a6f
12 touches
15 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xaa3b4402…74e6
0x34b655…2a6f
4 touches
1 conflict
0xcdf922ae…e126
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
15 conflicts on slot 0x8ac18b8d23…920c1c
Audit this contract →
← previous block·next block →recent activity