← previous blocknext block →recent activity
Analyzing
Block #96,123,253
9 transactions · 8 stateful · 2026-08-15 05:44:41 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,123,253 · 9 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
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc371f5e…0955
0x34b655…2a6f
4 touches
1 conflict
0x8c381258…46d0
0x34b655…2a6f
4 touches
1 conflict
0xc5c1e1b0…7a90
0x34b655…2a6f
4 touches
1 conflict
0xf2d8abfb…9cb6
0x34b655…2a6f
4 touches
1 conflict
0xf7933c2f…d104
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
2 touches
0 conflicts
0x7d07e5f7…6703
0x34b655…2a6f
2 touches
0 conflicts
0x9fbc6a76…9c29
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 0xfc371f5ead…b30955
Audit this contract →
← previous block·next block →recent activity