← previous blocknext block →recent activity
Analyzing
Block #108,470,112
18 transactions · 14 stateful · 2026-09-27 12:52:49 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,470,112 · 18 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
7w08w112w013w114w115w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2e1e311…5a5e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xccec837f…7ae4
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xfcd60863…48ea
0x34b655…2a6f
4 touches
1 conflict
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x1ad8153e…06bf
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
1 conflict on slot 0xb2e1e311d5…ce5a5e
Audit this contract →
← previous block·next block →recent activity