← previous blocknext block →recent activity
Analyzing
Block #108,676,561
20 transactions · 19 stateful · 2026-09-28 06:12:26 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,676,561 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w213w014w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0xa4f3fc53…7c45
0x508254…98bd
4 touches
1 conflict
0xdd8e8e57…0e7f
0x508254…98bd
4 touches
1 conflict
0xdd8e8e57…0ef5
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdb433f2f…3387
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity