← previous blocknext block →recent activity
Analyzing
Block #97,184,104
16 transactions · 13 stateful · 2026-08-18 22:53:29 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,184,104 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w49w513w015w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa93c5a4e…7108
0x34b655…2a6f
8 touches
6 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x1a2055c7…9054
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xa93c5a4e3a…137108
Audit this contract →
← previous block·next block →recent activity