← previous blocknext block →recent activity
Analyzing
Block #97,186,905
19 transactions · 17 stateful · 2026-08-18 23:07:54 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,186,905 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w08w19w010w111w212w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
14 touches
21 conflicts
0x00000000…000b
0x78999c…f371
14 touches
21 conflicts
0x00000000…000f
0x78999c…f371
14 touches
21 conflicts
0x00000000…000b
0x754704…b603
14 touches
21 conflicts
0x34b1e500…7687
0x754704…b603
14 touches
21 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf0a421ae…4638
0x851145…3f07
6 touches
3 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: 0x00000000…7da032
21 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity