← previous blocknext block →recent activity
Analyzing
Block #87,063,167
13 transactions · 10 stateful · 2026-07-11 13:29:38 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,063,167 · 13 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
1w02w17w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeea5b61d…2e58
0x34b655…2a6f
4 touches
1 conflict
0xd39bcac4…fcff
0x34b655…2a6f
4 touches
1 conflict
0xe9d235e0…3a43
0x34b655…2a6f
4 touches
1 conflict
0xe9d235e0…3a44
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
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 0xeea5b61de2…ca2e58
Audit this contract →
← previous block·next block →recent activity