← previous blocknext block →recent activity
Analyzing
Block #96,371,890
8 transactions · 7 stateful · 2026-08-16 02:35:17 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,371,890 · 8 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
3w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe46df8d3…e453
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
0x34b655…2a6f
4 touches
1 conflict
0x38badd90…a68c
0x34b655…2a6f
4 touches
1 conflict
0x8817ea9b…8b07
0x34b655…2a6f
4 touches
1 conflict
0x74461827…2bbb
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
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: Perpl
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity