← previous blocknext block →recent activity
Analyzing
Block #95,554,191
14 transactions · 12 stateful · 2026-08-13 06:00:54 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,554,191 · 14 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
2w03w04w15w18w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7c9b2b…6201
0x34b655…2a6f
4 touches
1 conflict
0xa7d90896…f395
0x34b655…2a6f
4 touches
1 conflict
0xc1ce1b01…90e2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x3fcb7de0…0bb1
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
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: Perpl
1 conflict on slot 0xee7c9b2bb2…bd6201
Audit this contract →
← previous block·next block →recent activity