← previous blocknext block →recent activity
Analyzing
Block #86,327,996
16 transactions · 11 stateful · 2026-07-08 03:34:23 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,327,996 · 16 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
4w07w19w110w211w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 conflicts
0xfa1a8731…ca65
0x34b655…2a6f
6 touches
3 conflicts
0x37ef764c…4c33
0x34b655…2a6f
4 touches
1 conflict
0x534f8b61…a9d6
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity