← previous blocknext block →recent activity
Analyzing
Block #86,362,752
17 transactions · 12 stateful · 2026-07-08 07:26:24 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,362,752 · 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
2w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe73b9841…932f
0x34b655…2a6f
3 touches
1 conflict
0x1a0e36a8…9acf
0x065c9d…c394
2 touches
0 conflicts
0x29811d8b…bc27
0x065c9d…c394
2 touches
0 conflicts
0x36e50335…c424
0x065c9d…c394
2 touches
0 conflicts
0xabb8c838…6c3b
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity