← previous blocknext block →recent activity
Analyzing
Block #108,467,015
23 transactions · 20 stateful · 2026-09-27 12:37:14 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,467,015 · 23 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
2w08w09w112w013w214w315w416w317w518w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe65bb7b…12d7
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x7b8805d1…1078
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xd6649475…a04f
0x34b655…2a6f
6 touches
3 conflicts
0x70dad334…73f8
0x34b655…2a6f
6 touches
3 conflicts
0xcd0e79e1…4c56
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 0xfe65bb7b2d…7112d7
Audit this contract →
← previous block·next block →recent activity