← previous blocknext block →recent activity
Analyzing
Block #87,410,418
17 transactions · 16 stateful · 2026-07-13 04:11:54 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,410,418 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w110w211w012w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x9e49f754…23a2
0x34b655…2a6f
6 touches
3 conflicts
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0xd69f26b4…c204
0x2a68ba…90c5
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xc335872c…4214
0x34b655…2a6f
4 touches
1 conflict
0xc3855e48…5859
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
3 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity