← previous blocknext block →recent activity
Analyzing
Block #106,300,493
12 transactions · 12 stateful · 2026-09-19 22:49:24 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,300,493 · 12 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
2w03w14w05w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf01d7021…9d29
0x6f6493…b480
10 touches
10 conflicts
0xa539e96e…c209
0x6f6493…b480
10 touches
10 conflicts
0xc5acd76c…ac3a
0x6f6493…b480
10 touches
10 conflicts
0xd03fd1a1…e8dd
0x6f6493…b480
10 touches
10 conflicts
0xd71877d4…67a0
0x6f6493…b480
10 touches
10 conflicts
0xdc17eb9e…2763
0x6f6493…b480
10 touches
10 conflicts
0xef961c5f…29bd
0x6f6493…b480
10 touches
10 conflicts
0x1b58e87a…ef58
0x6f6493…b480
10 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 0xf01d7021b0…379d29
Audit this contract →
← previous block·next block →recent activity