← previous blocknext block →recent activity
Analyzing
Block #95,413,613
13 transactions · 13 stateful · 2026-08-12 18:13:35 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,413,613 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x3beed133…720d
0x34b655…2a6f
4 touches
1 conflict
0x72a85328…2dc2
0x34b655…2a6f
4 touches
1 conflict
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x086fd05c…ebf0
0x34b655…2a6f
2 touches
0 conflicts
0x0afe708f…36f6
0x34b655…2a6f
2 touches
0 conflicts
0x185538b8…9b85
0x34b655…2a6f
2 touches
0 conflicts
0x25f83793…0646
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 0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block·next block →recent activity