← previous blocknext block →recent activity
Analyzing
Block #96,554,393
12 transactions · 12 stateful · 2026-08-16 17:53:28 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,554,393 · 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
2w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x466c9e6a…e9de
0x34b655…2a6f
4 touches
1 conflict
0x475bdffd…9a36
0x34b655…2a6f
4 touches
1 conflict
0x972e38eb…dc76
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xe8ea7440…3006
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
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 0x466c9e6a9e…88e9de
Audit this contract →
← previous block·next block →recent activity