← previous blocknext block →recent activity
Analyzing
Block #87,306,475
24 transactions · 19 stateful · 2026-07-12 16:36:40 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,306,475 · 24 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
2w03w14w05w16w07w19w110w211w314w217w018w122w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc628a0a0…22e5
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xa05444cf…cd70
0x34b655…2a6f
6 touches
3 conflicts
0x460a21c2…87f1
0x34b655…2a6f
6 touches
3 conflicts
0x5e47cbde…9659
0x34b655…2a6f
4 touches
1 conflict
0x63b15849…80b2
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0xc628a0a055…ab22e5
Audit this contract →
← previous block·next block →recent activity