← previous blocknext block →recent activity
Analyzing
Block #106,190,921
21 transactions · 19 stateful · 2026-09-19 13:37:53 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,190,921 · 21 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
1w02w13w04w18w010w113w214w315w419w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892587dc…c0ff
0x34b655…2a6f
10 touches
10 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
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 0x892587dc9c…f8c0ff
Audit this contract →
← previous block·next block →recent activity