← previous blocknext block →recent activity
Analyzing
Block #96,257,517
12 transactions · 10 stateful · 2026-08-15 17:00:02 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,257,517 · 12 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
1w02w03w04w15w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2db6e7a…d074
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x95ea33cc…0339
0x34b655…2a6f
4 touches
1 conflict
0xa771fb55…48d2
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 0xc2db6e7a2c…ddd074
Audit this contract →
← previous block·next block →recent activity