← previous blocknext block →recent activity
Analyzing
Block #87,456,324
14 transactions · 12 stateful · 2026-07-13 09:18:49 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,456,324 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xb7e6d391…2f76
0x34b655…2a6f
4 touches
1 conflict
0x191c9934…f4f4
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x736974b6…87a6
0x000000…012a
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x7730bc45…be06
0x01bff4…1071
2 touches
0 conflicts
0xb1a4d6b6…304f
0x01bff4…1071
2 touches
0 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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity