← previous blocknext block →recent activity
Analyzing
Block #106,034,176
14 transactions · 13 stateful · 2026-09-19 00:29:04 UTC
Parallelism
79/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,034,176 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dabd855…8ffb
0x34b655…2a6f
4 touches
1 conflict
0x9a527fe2…af1c
0x34b655…2a6f
4 touches
1 conflict
0x9cf9bac2…dee7
0x34b655…2a6f
4 touches
1 conflict
0xbee1499c…f426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfee8db15…cd58
0x34b655…2a6f
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
2 touches
0 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
1 conflict on slot 0x5dabd85549…798ffb
Audit this contract →
← previous block·next block →recent activity