← previous blocknext block →recent activity
Analyzing
Block #96,017,074
19 transactions · 19 stateful · 2026-08-14 20:50:37 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,017,074 · 19 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
1w02w16w17w29w010w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xb5ad11cb…71dd
0x34b655…2a6f
6 touches
3 conflicts
0x9d34cc12…59a6
0x34b655…2a6f
6 touches
3 conflicts
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x4e621c19…6089
0x34b655…2a6f
4 touches
1 conflict
0x5ef8a7e4…9f90
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 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity