← previous blocknext block →recent activity
Analyzing
Block #96,014,186
14 transactions · 12 stateful · 2026-08-14 20:36:01 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,014,186 · 14 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
2w03w04w16w17w28w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f24
0x34b655…2a6f
4 touches
1 conflict
0xa354eb2f…62ac
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: 0x33176be2…ede078
1 conflict on slot 0x09106a952c…111467
Audit this contract →
← previous block·next block →recent activity