← previous blocknext block →recent activity
Analyzing
Block #86,362,802
16 transactions · 14 stateful · 2026-07-08 07:26:44 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,362,802 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x55b69629…0d5e
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0176c0a2…d17d
0x065c9d…c394
2 touches
0 conflicts
0x11a75710…382f
0x065c9d…c394
2 touches
0 conflicts
0x148dc457…e120
0x065c9d…c394
2 touches
0 conflicts
0x2b235d67…9ecb
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 0x16a8cd0cae…8827bd
Audit this contract →
← previous block·next block →recent activity