← previous blocknext block →recent activity
Analyzing
Block #97,567,381
17 transactions · 13 stateful · 2026-08-20 07:35:41 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,567,381 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w112w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63d7e3d6…5eb7
0x34b655…2a6f
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x38c47502…1005
0x34b655…2a6f
2 touches
0 conflicts
0x4f6e12af…0385
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x63d7e3d647…fc5eb7
Audit this contract →
← previous block·next block →recent activity