← previous blocknext block →recent activity
Analyzing
Block #86,947,283
15 transactions · 15 stateful · 2026-07-11 00:35:22 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,947,283 · 15 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
1w02w17w08w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2d3fe13…b827
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2efac4f6…3abf
0x34b655…2a6f
4 touches
1 conflict
0x42381268…420e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x79ace5b6…8d37
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
1 conflict on slot 0xd2d3fe1336…0db827
Audit this contract →
← previous block·next block →recent activity