← previous blocknext block →recent activity
Analyzing
Block #96,020,927
8 transactions · 7 stateful · 2026-08-14 21:10:00 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,020,927 · 8 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
3w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x9215045f…42c5
0x065c9d…c394
3 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x31bd96a2…88b0
0x065c9d…c394
2 touches
0 conflicts
0x4ab7c029…0e71
0x065c9d…c394
2 touches
0 conflicts
0x6fbca386…6130
0x065c9d…c394
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity