← previous blocknext block →recent activity
Analyzing
Block #97,197,248
22 transactions · 18 stateful · 2026-08-19 00:00:00 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,197,248 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w19w010w111w012w119w020w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
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 0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block·next block →recent activity