← previous blocknext block →recent activity
Analyzing
Block #106,186,147
11 transactions · 11 stateful · 2026-09-19 13:13:52 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,186,147 · 11 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
2w03w14w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x88e99f62…ff26
0x34b655…2a6f
4 touches
1 conflict
0xa14a0c4b…becc
0x34b655…2a6f
3 touches
1 conflict
0x06ce5d4b…c122
0x34ae4d…3fc5
2 touches
0 conflicts
0x0145aa28…106b
0x34b655…2a6f
2 touches
0 conflicts
0x1b9758a0…ebb2
0x34b655…2a6f
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity