← previous blocknext block →recent activity
Analyzing
Block #97,368,537
23 transactions · 20 stateful · 2026-08-19 14:30:33 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,368,537 · 23 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
2w03w14w08w29w110w311w415w517w022w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x70cfbacf…5c46
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0x7a606d8a…9700
0x34b655…2a6f
4 touches
1 conflict
0x864d29cb…5ee2
0x34b655…2a6f
4 touches
1 conflict
0xa73fd363…97fd
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity