← previous blocknext block →recent activity
Analyzing
Block #108,103,073
16 transactions · 15 stateful · 2026-09-26 06:05:37 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,103,073 · 16 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
4w05w18w09w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x56751239…b935
0x34b655…2a6f
3 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
2 touches
0 conflicts
0x29f3234a…076f
0x34b655…2a6f
2 touches
0 conflicts
0x3162352e…ff9b
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 0x309ef36779…d6e8a1
Audit this contract →
← previous block·next block →recent activity