← previous blocknext block →recent activity
Analyzing
Block #86,244,246
17 transactions · 13 stateful · 2026-07-07 18:15:09 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,244,246 · 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
3w04w05w16w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x4966202a…d848
0x065c9d…c394
2 touches
0 conflicts
0x80c5d511…5afd
0x065c9d…c394
2 touches
0 conflicts
0xa63a9a65…2eab
0x065c9d…c394
2 touches
0 conflicts
0xde6a79d6…4af2
0x065c9d…c394
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
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 0xd800e635bc…14b1d7
Audit this contract →
← previous block·next block →recent activity