← previous blocknext block →recent activity
Analyzing
Block #96,684,778
14 transactions · 11 stateful · 2026-08-17 04:49:15 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,684,778 · 14 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
2w03w04w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a47a02…d364
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0x4bfa5f7e…cb5c
0x34b655…2a6f
4 touches
1 conflict
0x40442d27…fafc
0x34b655…2a6f
2 touches
0 conflicts
0x4850e38b…2306
0x34b655…2a6f
2 touches
0 conflicts
0x752f2b59…7187
0x34b655…2a6f
2 touches
0 conflicts
0x921a58d1…db22
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 0xb5a47a02cd…bfd364
Audit this contract →
← previous block·next block →recent activity