← previous blocknext block →recent activity
Analyzing
Block #87,306,925
13 transactions · 13 stateful · 2026-07-12 16:39:41 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,306,925 · 13 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
2w03w14w06w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974c36fe…1cd7
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x06e5a219…0058
0x34b655…2a6f
4 touches
1 conflict
0x68ebc592…026d
0x40c49f…2af0
2 touches
0 conflicts
0x6a7b9480…7933
0x40c49f…2af0
2 touches
0 conflicts
0xcd98a779…23ee
0x40c49f…2af0
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 0x974c36fe03…4f1cd7
Audit this contract →
← previous block·next block →recent activity