← previous blocknext block →recent activity
Analyzing
Block #107,839,435
21 transactions · 21 stateful · 2026-09-25 07:58:42 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,839,435 · 21 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
3w04w15w210w011w312w013w114w215w016w317w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d63456d…6681
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x66fc0764…05fd
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x1fe3f219…0f21
0x34b655…2a6f
6 touches
3 conflicts
0x0b01063c…fd72
0x851145…3f07
4 touches
1 conflict
0x1f5f0ac4…5f10
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
3 conflicts on slot 0x5d63456df3…326681
Audit this contract →
← previous block·next block →recent activity