← previous blocknext block →recent activity
Analyzing
Block #97,369,740
20 transactions · 17 stateful · 2026-08-19 14:36:39 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,369,740 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w09w010w111w012w214w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18906a6…d2e3
0x34b655…2a6f
8 touches
6 conflicts
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0x20d87ce7…4436
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x0d67b66f…c9b1
0x34b655…2a6f
4 touches
1 conflict
0x3ecbdf2f…b65a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc755c95b…6814
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
6 conflicts on slot 0xf18906a60b…97d2e3
Audit this contract →
← previous block·next block →recent activity