← previous blocknext block →recent activity
Analyzing
Block #97,476,446
14 transactions · 14 stateful · 2026-08-19 23:56:40 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,476,446 · 14 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
1w02w03w14w110w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x7cac81c0…70fc
0x34b655…2a6f
4 touches
1 conflict
0x4ff02e2d…eb25
0x065c9d…c394
2 touches
0 conflicts
0x626c2658…cce7
0x065c9d…c394
2 touches
0 conflicts
0xfb246666…5121
0x065c9d…c394
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity