← previous blocknext block →recent activity
Analyzing
Block #86,812,045
26 transactions · 19 stateful · 2026-07-10 09:31:10 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,812,045 · 26 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
1w02w14w214w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4bdabd…ffba
0x34b655…2a6f
10 touches
10 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
10 touches
10 conflicts
0xb06917e8…6985
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
10 touches
10 conflicts
0xb8fccd1b…b5f2
0x69df8a…6292
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
10 conflicts on slot 0x4f4bdabdf3…ecffba
Audit this contract →
← previous block·next block →recent activity