← previous blocknext block →recent activity
Analyzing
Block #86,244,862
28 transactions · 23 stateful · 2026-07-07 18:19:16 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,244,862 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w19w011w115w116w017w118w219w120w021w122w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9a8e72…7138
0x43cf54…7777
6 touches
3 conflicts
0x06e0630c…b45d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x397501e2…9a12
0x34b655…2a6f
4 touches
1 conflict
0x667658e1…e172
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
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: 0x43cf5407…d87777
3 conflicts on slot 0x1e9a8e7203…ed7138
Audit this contract →
← previous block·next block →recent activity