← previous blocknext block →recent activity
Analyzing
Block #87,703,246
26 transactions · 23 stateful · 2026-07-14 12:50:46 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,703,246 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w08w09w110w211w312w415w517w118w122w523w624w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0b11b7e3…1ded
0x34b655…2a6f
4 touches
1 conflict
0x11376762…a408
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x21605a79…d719
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity