← previous blocknext block →recent activity
Analyzing
Block #96,363,672
6 transactions · 6 stateful · 2026-08-16 01:53:56 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,363,672 · 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x2ad2e6d1…e192
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2dfcc03e…8aa0
0x34b655…2a6f
2 touches
0 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
2 touches
0 conflicts
0x63bed776…8d4a
0x34b655…2a6f
2 touches
0 conflicts
0x63bed776…8d4b
0x34b655…2a6f
2 touches
0 conflicts
0x77704719…12d9
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity