← previous blocknext block →recent activity
Analyzing
Block #97,495,931
24 transactions · 22 stateful · 2026-08-20 01:34:41 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,495,931 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w09w010w112w113w215w016w117w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x12070f84…331c
0xa6afd3…d132
4 touches
1 conflict
0xb5e46043…abcd
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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
3 conflicts on slot 0xda1f3e2ca4…a6b73d
Audit this contract →
← previous block·next block →recent activity