← previous blocknext block →recent activity
Analyzing
Block #86,363,554
18 transactions · 15 stateful · 2026-07-08 07:31:41 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,363,554 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w110w011w114w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa2dd7133…24d0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0xb98979…2361
4 touches
1 conflict
0x00000000…0000
0xb98979…2361
4 touches
1 conflict
0x40fd70b1…7250
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0xb98979…2361
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity