← previous blocknext block →recent activity
Analyzing
Block #107,814,446
23 transactions · 19 stateful · 2026-09-25 05:52:56 UTC
Parallelism
52/100
Blocked
63%
Avg conflicts / tx
2.43
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #107,814,446 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w513w614w715w817w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b76a1fb…fdfc
0x34b655…2a6f
20 touches
45 conflicts
0x24ac56e6…32b1
0x34b655…2a6f
18 touches
36 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
16 touches
28 conflicts
0x2130a548…c1de
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x4611acd1…c536
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xdc16b418…2f5d
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x2b76a1fb53…5afdfc
Audit this contract →
← previous block·next block →recent activity