← previous blocknext block →recent activity
Analyzing
Block #86,514,192
30 transactions · 26 stateful · 2026-07-09 00:18:24 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,514,192 · 30 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
1w04w05w16w27w38w49w110w011w113w019w220w326w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x79250c04…e936
0x8d1565…6723
6 touches
3 conflicts
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
6 touches
3 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: 0x8d156514…236723
10 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity