← previous blocknext block →recent activity
Analyzing
Block #96,125,896
18 transactions · 16 stateful · 2026-08-15 05:57:59 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,125,896 · 18 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
3w05w17w08w19w210w311w413w114w015w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
10 touches
10 conflicts
0x09106a95…1467
0x33176b…e078
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x4659c18a…cc29
0x34b655…2a6f
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc7d08bca…e210
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0x59df8637…6d2780
10 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity