← previous blocknext block →recent activity
Analyzing
Block #97,684,710
18 transactions · 17 stateful · 2026-08-20 17:35:19 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,684,710 · 18 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
2w03w14w05w06w17w28w310w411w515w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56bb09e…9c88
0x34b655…2a6f
8 touches
6 conflicts
0xab9cb617…561d
0x34b655…2a6f
4 touches
1 conflict
0xad0095f8…4ccb
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xc56bb09e4e…b79c88
Audit this contract →
← previous block·next block →recent activity