← previous blocknext block →recent activity
Analyzing
Block #106,945,658
15 transactions · 14 stateful · 2026-09-22 04:57:33 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,945,658 · 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
2w03w14w27w08w19w210w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37eb66f0…f797
0x34b655…2a6f
8 touches
6 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0xe6c1556a…9284
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
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
6 conflicts on slot 0x37eb66f086…06f797
Audit this contract →
← previous block·next block →recent activity