← previous blocknext block →recent activity
Analyzing
Block #106,958,336
21 transactions · 21 stateful · 2026-09-22 06:01:22 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,958,336 · 21 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
1w02w03w05w06w110w011w112w213w316w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x3e9bccd1…9cc9
0x34b655…2a6f
4 touches
1 conflict
0x4f3612e6…cb3f
0x34b655…2a6f
4 touches
1 conflict
0x704a8131…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity