← previous blocknext block →recent activity
Analyzing
Block #95,637,803
15 transactions · 14 stateful · 2026-08-13 13:01:28 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,637,803 · 15 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
2w03w14w25w36w39w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05f08c91…aa59
0x968279…9342
4 touches
1 conflict
0x05f08c91…aa5e
0x968279…9342
4 touches
1 conflict
0x05f08c91…aa5d
0x968279…9342
4 touches
1 conflict
0x05f08c91…aa5a
0x968279…9342
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x05f08c912d…34aa59
Audit this contract →
← previous block·next block →recent activity