← previous blocknext block →recent activity
Analyzing
Block #108,503,150
17 transactions · 16 stateful · 2026-09-27 15:39:10 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,503,150 · 17 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
5w07w18w210w011w112w113w215w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xfc51df41…9981
0x34b655…2a6f
4 touches
1 conflict
0x04667e1e…98eb
0x34b655…2a6f
4 touches
1 conflict
0x17c3cde7…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x448bcdd3…522f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
1 conflict on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity