← previous blocknext block →recent activity
Analyzing
Block #95,539,834
13 transactions · 12 stateful · 2026-08-13 04:48:42 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,539,834 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a08ca7f…6546
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x203f132b…89fc
0x34b655…2a6f
2 touches
0 conflicts
0x3c9835fe…6fde
0x34b655…2a6f
2 touches
0 conflicts
0x3cbfa5aa…cc9b
0x34b655…2a6f
2 touches
0 conflicts
0x5e78c401…7a7e
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x5a08ca7f8c…756546
Audit this contract →
← previous block·next block →recent activity