← previous blocknext block →recent activity
Analyzing
Block #86,448,736
19 transactions · 19 stateful · 2026-07-08 17:00:59 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,448,736 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w09w110w312w416w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x080ec687…da80
0x34b655…2a6f
6 touches
3 conflicts
0x6fd328f3…701f
0x34b655…2a6f
6 touches
3 conflicts
0x62d6e82b…a750
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4bfbf321…d4f2
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
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 0x080ec68796…07da80
Audit this contract →
← previous block·next block →recent activity