← previous blocknext block →recent activity
Analyzing
Block #87,310,417
13 transactions · 12 stateful · 2026-07-12 17:03:02 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,310,417 · 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
1w02w13w06w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb13b96bd…a3cb
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb0
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x198bae6a…f31c
0x34b655…2a6f
4 touches
1 conflict
0x37ee30c9…9e70
0x34b655…2a6f
4 touches
1 conflict
0x67cb4c75…f948
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0xb13b96bd5b…77a3cb
Audit this contract →
← previous block·next block →recent activity