← previous blocknext block →recent activity
Analyzing
Block #96,121,392
6 transactions · 4 stateful · 2026-08-15 05:35:18 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,121,392 · 6 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
1w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fee36ab…1014
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0xfc371f5e…0955
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x2a65fc9b…267c
0x34b655…2a6f
2 touches
0 conflicts
0x3ef8d2ff…b91e
0x34b655…2a6f
2 touches
0 conflicts
0x57528477…786d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5fee36aba4…1b1014
Audit this contract →
← previous block·next block →recent activity