← previous blocknext block →recent activity
Analyzing
Block #86,453,359
13 transactions · 11 stateful · 2026-07-08 17:31:54 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,453,359 · 13 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
1w02w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2d122c22…afca
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x88548dc6…015a
0x065c9d…c394
3 touches
1 conflict
0xae33ba3d…e9aa
0x065c9d…c394
3 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
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 0x747f609d18…eb1555
Audit this contract →
← previous block·next block →recent activity