← previous blocknext block →recent activity
Analyzing
Block #86,493,805
16 transactions · 14 stateful · 2026-07-08 22:02:27 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,493,805 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60c7217a…8c94
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x80a17b8a…3681
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
0x065c9d…c394
2 touches
0 conflicts
0xf024bd1d…ba98
0x065c9d…c394
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
1 conflict on slot 0x60c7217a29…038c94
Audit this contract →
← previous block·next block →recent activity