← previous blocknext block →recent activity
Analyzing
Block #108,960,712
22 transactions · 19 stateful · 2026-09-29 06:06:49 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,960,712 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w010w011w112w213w314w117w419w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x174f9ecc…6481
0x34b655…2a6f
8 touches
6 conflicts
0xd80cb602…d50a
0x34b655…2a6f
8 touches
6 conflicts
0xc53799eb…d928
0x34b655…2a6f
8 touches
6 conflicts
0x2b60abad…2240
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
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
6 conflicts on slot 0x174f9eccb5…8e6481
Audit this contract →
← previous block·next block →recent activity