← previous blocknext block →recent activity
Analyzing
Block #108,515,219
28 transactions · 27 stateful · 2026-09-27 16:39:55 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,515,219 · 28 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
4w05w110w011w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe2c32146…d7d7
0x34b655…2a6f
6 touches
3 conflicts
0x5900e8aa…2391
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x88cf2d31…3d64
0x34b655…2a6f
4 touches
1 conflict
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
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 0x3cb7ee74c7…7db8a5
Audit this contract →
← previous block·next block →recent activity