← previous blocknext block →recent activity
Analyzing
Block #106,469,744
21 transactions · 19 stateful · 2026-09-20 13:01:14 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,469,744 · 21 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
1w03w14w05w112w013w014w115w216w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33365a6a…7e0b
0x34b655…2a6f
10 touches
10 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0x2f50c84a…3640
0x34b655…2a6f
4 touches
1 conflict
0x3c70ac8d…eaf2
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x5b7fec07…7153
0x34b655…2a6f
4 touches
1 conflict
0x844fc686…2d23
0x34b655…2a6f
4 touches
1 conflict
0x93979174…1832
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 0x33365a6a88…d17e0b
Audit this contract →
← previous block·next block →recent activity