← previous blocknext block →recent activity
Analyzing
Block #108,350,891
17 transactions · 14 stateful · 2026-09-27 02:52:48 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,350,891 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w311w012w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xb358e96b…6fc4
0x34b655…2a6f
6 touches
3 conflicts
0x5adb7fa8…99ad
0x34b655…2a6f
4 touches
1 conflict
0x4aa8b305…4ace
0xcc9410…4c10
4 touches
1 conflict
0x3c202c1b…d698
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
3 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity