← previous blocknext block →recent activity
Analyzing
Block #86,493,616
9 transactions · 7 stateful · 2026-07-08 22:01:11 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,493,616 · 9 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf63d1c19…4e18
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5f34fd08…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x90dab4af…097e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0001
0x0cc02c…75b2
2 touches
0 conflicts
0x00000000…0006
0x0cc02c…75b2
2 touches
0 conflicts
0xa76783b8…c2e4
0x0cc02c…75b2
2 touches
0 conflicts
0x40c0484d…8192
0x188d58…ea8e
2 touches
0 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
1 conflict on slot 0xf63d1c1918…294e18
Audit this contract →
← previous block·next block →recent activity