← previous blocknext block →recent activity
Analyzing
Block #86,881,572
19 transactions · 17 stateful · 2026-07-10 17:16:16 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,881,572 · 19 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
1w02w14w05w16w29w010w111w113w114w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10cab052…8d64
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x153d1e25…10ea
0x34b655…2a6f
4 touches
1 conflict
0x2d8af94a…722c
0x34b655…2a6f
4 touches
1 conflict
0x347327ff…3863
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x10cab052f6…0e8d64
Audit this contract →
← previous block·next block →recent activity