← previous blocknext block →recent activity
Analyzing
Block #87,718,847
38 transactions · 35 stateful · 2026-07-14 14:35:23 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
2.47
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,718,847 · 38 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w29w310w411w512w613w714w817w118w219w321w123w224w429w130w533w735w1036w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xa6c9a33e…d839
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x78a19448…40e8
0x34b655…2a6f
8 touches
6 conflicts
0x84d74093…7808
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity