← previous blocknext block →recent activity
Analyzing
Block #106,435,732
23 transactions · 21 stateful · 2026-09-20 10:10:01 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,435,732 · 23 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
2w03w17w011w012w113w214w316w417w019w521w122w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5364a0e7…41fc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0x9708602e…de14
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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 0x5364a0e74e…8041fc
Audit this contract →
← previous block·next block →recent activity