← previous blocknext block →recent activity
Analyzing
Block #106,337,398
17 transactions · 17 stateful · 2026-09-20 01:55:07 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,337,398 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w18w29w312w413w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x100ec7e6…6b5a
0x34b655…2a6f
6 touches
3 conflicts
0x0d72fcee…4b28
0x34b655…2a6f
6 touches
3 conflicts
0x38faf16c…0987
0x34b655…2a6f
4 touches
1 conflict
0x5fedce9e…74cb
0x34b655…2a6f
4 touches
1 conflict
0x823a3658…acf6
0x34b655…2a6f
4 touches
1 conflict
0x87d58f4e…70c8
0x34b655…2a6f
4 touches
1 conflict
0x8f5d8267…0216
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity