← previous blocknext block →recent activity
Analyzing
Block #106,917,346
39 transactions · 38 stateful · 2026-09-22 02:35:03 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
2.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,917,346 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w010w111w212w313w414w515w616w717w119w120w821w922w1023w1124w1225w1329w232w334w935w1036w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c60fbcf…8744
0x34b655…2a6f
20 touches
45 conflicts
0x70986451…c6bd
0x34b655…2a6f
16 touches
28 conflicts
0x05ae81ac…b6d2
0x34b655…2a6f
16 touches
28 conflicts
0x251ee419…4404
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x6c60fbcffc…878744
Audit this contract →
← previous block·next block →recent activity