← previous blocknext block →recent activity
Analyzing
Block #97,529,209
17 transactions · 14 stateful · 2026-08-20 04:22:06 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,529,209 · 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
1w05w06w113w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xfafd2db2…acef
0x34b655…2a6f
3 touches
1 conflict
0x14ea9ada…e628
0x34b655…2a6f
2 touches
0 conflicts
0x34150e6b…c5b3
0x34b655…2a6f
2 touches
0 conflicts
0x35c37635…11a6
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 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity