← previous blocknext block →recent activity
Analyzing
Block #87,259,422
16 transactions · 16 stateful · 2026-07-12 11:22:08 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,259,422 · 16 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
1w02w17w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ac265cd…0253
0x34b655…2a6f
4 touches
1 conflict
0x896c6d38…425c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe9ac193d…f728
0x34b655…2a6f
4 touches
1 conflict
0xe9ac193d…f729
0x34b655…2a6f
4 touches
1 conflict
0xfbeb25a4…725a
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
1 conflict on slot 0x7ac265cd10…c30253
Audit this contract →
← previous block·next block →recent activity