← previous blocknext block →recent activity
Analyzing
Block #86,247,715
17 transactions · 14 stateful · 2026-07-07 18:38:22 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,247,715 · 17 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
4w05w112w013w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ebb62dc…818a
0x065c9d…c394
2 touches
0 conflicts
0x1eed4688…2bff
0x065c9d…c394
2 touches
0 conflicts
0x6e3952ec…f864
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
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 0x3bdd71a21a…eeb6eb
Audit this contract →
← previous block·next block →recent activity