← previous blocknext block →recent activity
Analyzing
Block #86,306,501
19 transactions · 18 stateful · 2026-07-08 01:10:45 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,306,501 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w113w014w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xd45e7a3b…85f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x77c441cc…ba48
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0xe3312997…60f5
0x065c9d…c394
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
1 conflict on slot 0xc5a1b2febf…f05369
Audit this contract →
← previous block·next block →recent activity