← previous blocknext block →recent activity
Analyzing
Block #95,543,673
19 transactions · 18 stateful · 2026-08-13 05:08:01 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,543,673 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w011w112w215w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd0919e62…a2a8
0x34b655…2a6f
6 touches
3 conflicts
0xf40e9839…0001
0x34b655…2a6f
4 touches
1 conflict
0xfc33a532…28e5
0x34b655…2a6f
4 touches
1 conflict
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6d
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity