← previous blocknext block →recent activity
Analyzing
Block #87,503,467
38 transactions · 24 stateful · 2026-07-13 14:34:04 UTC
Parallelism
87/100
Blocked
58%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,503,467 · 38 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
2w03w14w05w16w27w08w119w020w122w223w324w427w228w029w132w233w334w137w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x767799cd…f423
0xc8689a…ee79
6 touches
3 conflicts
0xa863a526…9995
0x34b655…2a6f
6 touches
3 conflicts
0xadd42cbc…24c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0xdc69def1…fa0b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity