← previous blocknext block →recent activity
Analyzing
Block #106,958,452
15 transactions · 15 stateful · 2026-09-22 06:01:57 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,958,452 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58c717c…8fc9
0x34b655…2a6f
6 touches
3 conflicts
0xa2fda9ea…b510
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x704a8131…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x37eb66f0…f797
0x34b655…2a6f
2 touches
0 conflicts
0x3bca67b5…842d
0x34b655…2a6f
2 touches
0 conflicts
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
3 conflicts on slot 0xf58c717cd9…968fc9
Audit this contract →
← previous block·next block →recent activity