← previous blocknext block →recent activity
Analyzing
Block #96,036,862
19 transactions · 18 stateful · 2026-08-14 22:30:11 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,036,862 · 19 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
2w03w14w07w18w010w011w112w213w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35ea14b4…30a2
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x0001f04e…9ed7
0x968279…9342
8 touches
6 conflicts
0x0001f04e…9ed8
0x968279…9342
8 touches
6 conflicts
0x0001f04e…9eda
0x968279…9342
8 touches
6 conflicts
0x35ea14b4…309c
0x968279…9342
8 touches
6 conflicts
0x35ea14b4…309d
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0x35ea14b4c3…0930a2
Audit this contract →
← previous block·next block →recent activity