← previous blocknext block →recent activity
Analyzing
Block #107,848,260
19 transactions · 16 stateful · 2026-09-25 08:43:07 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,848,260 · 19 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
2w03w06w17w08w19w210w311w412w513w614w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd344088c…806f
0x34b655…2a6f
14 touches
21 conflicts
0xecff7c35…1b43
0x34b655…2a6f
14 touches
21 conflicts
0x31d88d27…7617
0x34b655…2a6f
12 touches
15 conflicts
0x70335443…ff8e
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xfa2794a8…40de
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xd344088c78…71806f
Audit this contract →
← previous block·next block →recent activity