← previous blocknext block →recent activity
Analyzing
Block #106,385,646
30 transactions · 26 stateful · 2026-09-20 05:57:57 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,385,646 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w16w27w19w111w212w313w415w416w517w619w123w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e665745…8517
0x34b655…2a6f
16 touches
28 conflicts
0x3ca268be…8865
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x1e66574536…6d8517
Audit this contract →
← previous block·next block →recent activity