← previous blocknext block →recent activity
Analyzing
Block #107,813,516
22 transactions · 22 stateful · 2026-09-25 05:48:15 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,516 · 22 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
1w03w16w07w08w19w210w311w412w513w614w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1027d118…fd91
0x34b655…2a6f
12 touches
15 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa62dce79…e7ff
0x34b655…2a6f
8 touches
6 conflicts
0x33848157…61dc
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
15 conflicts on slot 0x1027d11834…75fd91
Audit this contract →
← previous block·next block →recent activity