← previous blocknext block →recent activity
Analyzing
Block #86,881,281
21 transactions · 14 stateful · 2026-07-10 17:14:19 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,881,281 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w010w111w214w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8391fb68…4c83
0x34b655…2a6f
4 touches
1 conflict
0x9d64d7f8…ce93
0x34b655…2a6f
4 touches
1 conflict
0x872f81ab…d1d6
0x065c9d…c394
3 touches
1 conflict
0x116cdd92…58f2
0x34b655…2a6f
2 touches
0 conflicts
0x14339c29…d1a8
0x34b655…2a6f
2 touches
0 conflicts
0x146d92ed…2a44
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity