← previous blocknext block →recent activity
Analyzing
Block #86,057,509
16 transactions · 15 stateful · 2026-07-06 21:28:41 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,057,509 · 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
2w03w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x10326aa1…38a3
0x34b655…2a6f
4 touches
1 conflict
0xf357ed8b…e65c
0x34b655…2a6f
3 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
2 touches
0 conflicts
0x40b8f0ac…20bb
0x34b655…2a6f
2 touches
0 conflicts
0x726752fc…813d
0x34b655…2a6f
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity