← previous blocknext block →recent activity
Analyzing
Block #96,115,258
10 transactions · 9 stateful · 2026-08-15 05:04:27 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,115,258 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fb1c078…8aae
0x968279…9342
4 touches
1 conflict
0x9fb1c078…8aa7
0x968279…9342
4 touches
1 conflict
0x9fb1c078…8aa8
0x968279…9342
4 touches
1 conflict
0x9fb1c078…8aab
0x968279…9342
4 touches
1 conflict
0x9fb1c078…8aac
0x968279…9342
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x839be85f…a40b
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: 0x96827978…f09342
1 conflict on slot 0x9fb1c078ee…1d8aae
Audit this contract →
← previous block·next block →recent activity