← previous blocknext block →recent activity
Analyzing
Block #106,934,570
30 transactions · 30 stateful · 2026-09-22 04:01:44 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.53
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,934,570 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w19w210w311w412w513w614w715w823w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58deff…c5d0
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0xdfac0724…d23e
0x34b655…2a6f
16 touches
28 conflicts
0xc44fc151…bd06
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
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
36 conflicts on slot 0x4e58deff76…56c5d0
Audit this contract →
← previous block·next block →recent activity