← previous blocknext block →recent activity
Analyzing
Block #106,015,384
17 transactions · 17 stateful · 2026-09-18 22:54:29 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,015,384 · 17 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
1w04w05w18w09w110w211w312w213w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a5379d…289d
0x73ca90…1130
8 touches
6 conflicts
0x16a5379d…289e
0x73ca90…1130
8 touches
6 conflicts
0x07ae82ab…f5ca
0x6f6493…b480
7 touches
6 conflicts
0x16c69f49…2d17
0x6f6493…b480
7 touches
6 conflicts
0x196fc98a…34f2
0x6f6493…b480
7 touches
6 conflicts
0x1a98baac…652c
0x6f6493…b480
7 touches
6 conflicts
0x1ebfc3ff…f820
0x6f6493…b480
7 touches
6 conflicts
0x35e0facc…c9b6
0x6f6493…b480
7 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: 0x73ca9094…0c1130
6 conflicts on slot 0x16a5379d71…d6289d
Audit this contract →
← previous block·next block →recent activity