← previous blocknext block →recent activity
Analyzing
Block #86,293,068
19 transactions · 13 stateful · 2026-07-07 23:41:00 UTC
Parallelism
89/100
Blocked
15%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,293,068 · 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
1w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0xa8c04ae6…4280
0x34b655…2a6f
4 touches
1 conflict
0x1d8a5ffb…d996
0x065c9d…c394
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
4 touches
1 conflict
0xddc0f050…9726
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
1 conflict on slot 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity