← previous blocknext block →recent activity
Analyzing
Block #107,815,371
15 transactions · 15 stateful · 2026-09-25 05:57:35 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,815,371 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w713w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
14 touches
21 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x13c65823…36ad
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x3c670f07…2b71
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x4611acd1…c536
0x34b655…2a6f
6 touches
3 conflicts
0x4a1553d9…655d
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 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity