← previous blocknext block →recent activity
Analyzing
Block #108,652,526
20 transactions · 19 stateful · 2026-09-28 04:11:24 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,652,526 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w19w011w112w114w215w316w417w518w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0x734d9ade…ce49
0x34b655…2a6f
4 touches
1 conflict
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity