← previous blocknext block →recent activity
Analyzing
Block #93,074,410
20 transactions · 18 stateful · 2026-08-04 13:36:54 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,074,410 · 20 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
1w03w04w16w17w08w19w210w312w215w016w117w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a9064c9…c8ca
0x34b655…2a6f
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x1a9064c924…9cc8ca
Audit this contract →
← previous block·next block →recent activity