← previous blocknext block →recent activity
Analyzing
Block #96,434,794
13 transactions · 11 stateful · 2026-08-16 07:51:37 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,434,794 · 13 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
4 touches
1 conflict
0x9e6be63e…d886
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
4 touches
1 conflict
0xeb5ec45d…2a85
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…641c
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 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity