← previous blocknext block →recent activity
Analyzing
Block #106,950,963
16 transactions · 15 stateful · 2026-09-22 05:24:15 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,963 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w110w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28611b1f…2187
0x34b655…2a6f
10 touches
10 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xeb179a44…5477
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1d81790c…b9f7
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 0x28611b1fc2…ce2187
Audit this contract →
← previous block·next block →recent activity