← previous blocknext block →recent activity
Analyzing
Block #96,124,377
12 transactions · 9 stateful · 2026-08-15 05:50:20 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,124,377 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf101bd5c…0d99
0x77d53b…8080
4 touches
1 conflict
0xd18e4cb7…88d4
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x4d6228eb…66e4
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
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: 0x77d53b3b…378080
1 conflict on slot 0xf101bd5c18…d20d99
Audit this contract →
← previous block·next block →recent activity