← previous blocknext block →recent activity
Analyzing
Block #86,084,541
11 transactions · 11 stateful · 2026-07-07 00:28:53 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,084,541 · 11 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
1w06w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x79fdf915…6ac7
0x34b655…2a6f
4 touches
1 conflict
0xbff4c9a8…ce2b
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x92e18ab1…e6f7
0x0594c7…a3be
2 touches
0 conflicts
0xa7eba144…e5cd
0x0594c7…a3be
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity