← previous blocknext block →recent activity
Analyzing
Block #87,629,438
22 transactions · 19 stateful · 2026-07-14 04:37:22 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,629,438 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w212w114w315w016w117w418w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x9aaca373…d7c0
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3bdfb…7537
0x34b655…2a6f
6 touches
3 conflicts
0xdb0641d8…20ed
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xa3489b05…18f1
0x34b655…2a6f
6 touches
3 conflicts
0x63f8a50d…333b
0x34b655…2a6f
4 touches
1 conflict
0x6bf71f68…fd07
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity