← previous blocknext block →recent activity
Analyzing
Block #106,189,157
28 transactions · 26 stateful · 2026-09-19 13:29:01 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,189,157 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w115w216w317w218w419w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8484e192…ad79
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xc3c0295b…86a9
0x34b655…2a6f
8 touches
6 conflicts
0x6603a09f…6ad7
0x34b655…2a6f
8 touches
6 conflicts
0xd7793452…ae6a
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
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
15 conflicts on slot 0x8484e192ad…76ad79
Audit this contract →
← previous block·next block →recent activity