← previous blocknext block →recent activity
Analyzing
Block #96,784,640
19 transactions · 15 stateful · 2026-08-17 13:11:31 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,784,640 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w09w310w413w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d1df17e…b68c
0x34b655…2a6f
12 touches
15 conflicts
0xd597209e…9800
0x34b655…2a6f
8 touches
6 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
8 touches
6 conflicts
0xffb2bfcf…b92a
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x7c09c53e…64b4
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x2d1df17e76…99b68c
Audit this contract →
← previous block·next block →recent activity