← previous blocknext block →recent activity
Analyzing
Block #86,327,990
32 transactions · 27 stateful · 2026-07-08 03:34:21 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,327,990 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w19w112w013w114w015w117w018w222w124w326w128w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x30faf03c…78b1
0x34b655…2a6f
4 touches
1 conflict
0x33329ed3…38c2
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x96dd83e650…3fa507
Audit this contract →
← previous block·next block →recent activity