← previous blocknext block →recent activity
Analyzing
Block #96,425,922
12 transactions · 9 stateful · 2026-08-16 07:07:00 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,425,922 · 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
1w02w13w17w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1faa605…f919
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x0e246445…9e0e
0x34b655…2a6f
4 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
4 touches
1 conflict
0x3727225e…a3cf
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x846cd867…f36c
0x34b655…2a6f
4 touches
1 conflict
0xa6848351…2238
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 0xf1faa605a5…02f919
Audit this contract →
← previous block·next block →recent activity