← previous blocknext block →recent activity
Analyzing
Block #87,421,737
28 transactions · 21 stateful · 2026-07-13 05:27:34 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,421,737 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w011w112w213w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x76196ad0…ce0c
0x34b655…2a6f
8 touches
6 conflicts
0xad95efd9…b4cf
0x34b655…2a6f
6 touches
3 conflicts
0x366f651e…6100
0x34b655…2a6f
6 touches
3 conflicts
0x5fda5ee7…68b7
0x34b655…2a6f
4 touches
1 conflict
0x67d8b71a…ee0f
0x34b655…2a6f
4 touches
1 conflict
0x6ca32a09…4e48
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity