← previous blocknext block →recent activity
Analyzing
Block #106,363,115
20 transactions · 19 stateful · 2026-09-20 04:04:33 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,363,115 · 20 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
2w06w17w210w011w112w213w314w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05c0c006…6048
0x6f6493…b480
9 touches
10 conflicts
0x05c0c006…604c
0x6f6493…b480
9 touches
10 conflicts
0x1bc26fb7…9335
0x6f6493…b480
9 touches
10 conflicts
0x328ea6b4…ea56
0x6f6493…b480
9 touches
10 conflicts
0x33aaafe0…b3ba
0x6f6493…b480
9 touches
10 conflicts
0x34509004…efa7
0x6f6493…b480
9 touches
10 conflicts
0x35a9c013…f7a5
0x6f6493…b480
9 touches
10 conflicts
0x38d05b00…868b
0x6f6493…b480
9 touches
10 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: 0x6f6493e3…08b480
10 conflicts on slot 0x05c0c006d9…586048
Audit this contract →
← previous block·next block →recent activity