← previous blocknext block →recent activity
Analyzing
Block #87,596,519
21 transactions · 17 stateful · 2026-07-14 00:57:13 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,596,519 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w28w010w111w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62222abd…e410
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x2be09ff3…ce49
0x34b655…2a6f
4 touches
1 conflict
0x2df6f59b…d662
0x34b655…2a6f
4 touches
1 conflict
0x342ae6d7…2e17
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 0x62222abdea…6fe410
Audit this contract →
← previous block·next block →recent activity