← previous blocknext block →recent activity
Analyzing
Block #106,156,008
13 transactions · 12 stateful · 2026-09-19 10:42:12 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,156,008 · 13 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
2w03w16w07w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb376d06…ecc3
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x93aaefce…5be5
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xb47d4bdd…6172
0x34b655…2a6f
4 touches
1 conflict
0xb546b952…cb29
0x34b655…2a6f
4 touches
1 conflict
0x26c599c1…706c
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 0xdb376d0665…39ecc3
Audit this contract →
← previous block·next block →recent activity