← previous blocknext block →recent activity
Analyzing
Block #86,448,332
24 transactions · 19 stateful · 2026-07-08 16:58:17 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,448,332 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w09w210w112w120w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd537abd7…104a
0x851145…3f07
4 touches
1 conflict
0xe0532746…0224
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8a751d7a…247c
0xa6afd3…d132
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity