← previous blocknext block →recent activity
Analyzing
Block #105,931,177
19 transactions · 18 stateful · 2026-09-18 15:50:31 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,931,177 · 19 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
2w04w05w16w07w08w210w012w113w314w416w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe796f8b7…ad55
0x34b655…2a6f
10 touches
10 conflicts
0x33838089…1837
0x34b655…2a6f
6 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x3ee13af7…3ccc
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x5b17b0ae…fccf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xe796f8b7af…c7ad55
Audit this contract →
← previous block·next block →recent activity