← previous blocknext block →recent activity
Analyzing
Block #106,421,330
17 transactions · 16 stateful · 2026-09-20 08:57:31 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,421,330 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w08w19w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xcf570cc1…b19c
0x99c7a7…8bf0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x5d4463c7…0c3e
0x754704…b603
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xd52cdd17f0…d5928b
Audit this contract →
← previous block·next block →recent activity