← previous blocknext block →recent activity
Analyzing
Block #108,469,586
14 transactions · 13 stateful · 2026-09-27 12:50:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,469,586 · 14 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
4w06w17w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4a5ebd3…ed89
0x34b655…2a6f
4 touches
1 conflict
0x728d5f1a…73c1
0x34b655…2a6f
4 touches
1 conflict
0x8cef29f5…776c
0x34b655…2a6f
4 touches
1 conflict
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0xc320245d…1302
0x34b655…2a6f
4 touches
1 conflict
0xc856ff11…2b9c
0x34b655…2a6f
4 touches
1 conflict
0x00533680…4021
0x34b655…2a6f
4 touches
1 conflict
0x132b9de1…183b
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 0xf4a5ebd337…f2ed89
Audit this contract →
← previous block·next block →recent activity