← previous blocknext block →recent activity
Analyzing
Block #108,350,863
8 transactions · 8 stateful · 2026-09-27 02:52:40 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,350,863 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0x630d3a92…b245
0x34b655…2a6f
4 touches
1 conflict
0xddd9d39e…0c69
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x88cf2d31…3d64
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x8fa4ba1b…750c
0x34b655…2a6f
2 touches
0 conflicts
0xb358e96b…6fc4
0x34b655…2a6f
2 touches
0 conflicts
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 0xc53799ebcf…a9d928
Audit this contract →
← previous block·next block →recent activity