← previous blocknext block →recent activity
Analyzing
Block #86,363,593
19 transactions · 17 stateful · 2026-07-08 07:31:57 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,363,593 · 19 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
1w02w17w09w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b18ba0…f380
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x807bf45f…5016
0x34b655…2a6f
4 touches
1 conflict
0x9659faf8…310c
0x34b655…2a6f
4 touches
1 conflict
0xa1ed9a98…f5e5
0x34b655…2a6f
4 touches
1 conflict
0x2aed5095…1d12
0xd32edf…ff58
3 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
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 0xa8b18ba0f2…07f380
Audit this contract →
← previous block·next block →recent activity