← previous blocknext block →recent activity
Analyzing
Block #85,583,717
12 transactions · 11 stateful · 2026-07-04 16:49:53 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,583,717 · 12 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x618bda4c…65e3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5accb062…6d13
0x34b655…2a6f
4 touches
1 conflict
0x1486184c…f1ae
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x7dbb8470…0f9f
0x5afd3e…7620
2 touches
0 conflicts
0xc22018e2…dc5d
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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 0x618bda4c5f…5965e3
Audit this contract →
← previous block·next block →recent activity