← previous blocknext block →recent activity
Analyzing
Block #96,369,004
15 transactions · 13 stateful · 2026-08-16 02:20:45 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,369,004 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w19w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1ea5e38…2867
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x06726618…fafd
0x34b655…2a6f
4 touches
1 conflict
0x16f2b4e1…e98b
0x34b655…2a6f
4 touches
1 conflict
0x5a0a2b03…ac50
0x34b655…2a6f
2 touches
0 conflicts
0x8ec95f2b…f4d7
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 0xd1ea5e386a…692867
Audit this contract →
← previous block·next block →recent activity